[
https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763517#action_12763517
]
Christophe Cordenier commented on TAP5-879:
-------------------------------------------
The question is : more generally, Is this a good solution to ignore a request
if the request has activation parameter and the page has not the corresponding
method ? And especially if the application has an index page that is used by
default.
In the case of an Event request, an exception is thrown that make sense from a
development view.
In a Render request, ignoring the request should be a solution.
What about a parameter for this kind of feature ? (Strict activation context
checking)
> 404 is never raised automatically if the application has an index page.
> -----------------------------------------------------------------------
>
> Key: TAP5-879
> URL: https://issues.apache.org/jira/browse/TAP5-879
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Christophe Cordenier
>
> The default behavior of PageRenderDispatcher when a user access to a URL like
> 'http://localhost/demo/blah' (where 'demo' is the application context and
> 'blah' is a page that does not exist) is to translate to
> 'http://localhost/demo/index/blah' if an index page exists even if it has no
> activation method.
> It could be a better solution to check if a the index page has an activation
> method with the corresponding parameter number and type, and automatically
> raise a http 404 if not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
