You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/06/22 17:02:26 UTC

[jira] Commented: (TAPESTRY-1595) TapestryFilter throws IllegalArgumentException if request path for non-Tapestry page contains '.' or ':'

    [ https://issues.apache.org/jira/browse/TAPESTRY-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507410 ] 

Howard M. Lewis Ship commented on TAPESTRY-1595:
------------------------------------------------

The filter automatically ignores real resources in the web context.

I think what we need is a filter, within Tapestry, about additional paths that should defer to the servlet container.

I think a service with a configuration in the form of a bunch of regular expressions would get the job done.

It would be better if Tapestry could adapt to what's present in web.xml, but the Servlet API doesn't give access to that.  Maybe Servlet API 3.0.

> TapestryFilter throws IllegalArgumentException if request path for non-Tapestry page contains '.' or ':'
> --------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1595
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1595
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: Douglas Hauge
>         Attachments: Tapestry_Exception_Page.html
>
>
> For pages not handled by Tapestry, it should pass control along to next filter in chain, which it does for paths that do not contain '.' or ':'. For example, if '/foo/bar' is not a page recognized by Tapestry, a URI with the path 
> /foo/bar/image.gif
> will cause an 'IllegalArgumentException' with the message 'Unable to resolve page 'foo/bar/image' to a known page name. ...'
> while
> /foo/bar/image_gif
> will be properly forwarded to the filters after TapestryFilter.
> The problem seems to be that 'ComponentActionDispatcher' will attempt to process any path that contains '.' or ':', unlike 'PageRenderDispatcher' which explicitly checks that it recognizes a prefix of the path.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org