[
https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768203#action_12768203
]
Christophe Cordenier commented on TAP5-879:
-------------------------------------------
Hello
I have started to implement a solution , it still need to be tested, but i
would like to have your opinion on the implementation choice
1. In the PageRenderRequestHandlerImpl and ComponentEventRequestHandlerImpl
a. Verify that the activate event has been handled if the request contains
activation parameters
b. If yes, then continue
c. If no, then add an attribute in the request and return
2. In the dispatcher level
a. Each time a request handler (page render or component event) is called,
check the request if the attribute is not present
b. If yes then return false
c. If no then return true
Regards,
Christophe.
> 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.
