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
will cause an 'IllegalArgumentException' with the message 'Unable to resolve page 'foo/bar/image' to a known page name. ...'
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.
|Workflow||Default workflow, editable Closed status [ 12568440 ]||jira [ 12591493 ]|
|Workflow||jira [ 12406827 ]||Default workflow, editable Closed status [ 12568440 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Fix Version/s||5.0.8 [ 12312898 ]|
|Summary||TapestryFilter throws IllegalArgumentException if request path for non-Tapestry page contains '.' or ':'||Add support for ignoring paths that belong to other servlets in the web application|
|Priority||Major [ 3 ]||Minor [ 4 ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|