[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725340#comment-13725340
]
Lenny Primak commented on TAP5-2070:
------------------------------------
I would love to get this fix incorporated. I currently use this code in the
index page to work around this issue:
8 /**
9 * Restore 404 Not Found errors
10 * @param context
11 * @return
12 */
13 HttpError onActivate(EventContext context)
14 {
15 if (context.getCount() == 0)
16 {
17 return null;
18 }
19
20 return new HttpError(404, "Resource not found.");
21 }
> Respond with a HTTP 404 if the page is activated with an activation context
> not explicitly supported by the page itself
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-2070
> URL: https://issues.apache.org/jira/browse/TAP5-2070
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Massimo Lusetti
> Assignee: Massimo Lusetti
> Attachments:
> 0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
>
>
> The behavior from day one for pages within Tapestry is to being able to serve
> requests that come with an activation context with more parameters that the
> ones declared by the page itself.
> This feature lead the framework to serve requests that comes to URL which are
> not explicitly declared by the pages, for example a page named: Super with an
> activation event handler method like this one:
> onActivate(String character) { ... }
> will finely serve requests for:
> /super/mario
> /super/luigi
> /super/wario
> /super/waluigi
> but it will also serve requests for:
> /super/mario/luigi/wario/waluigi
> This issue is to change that behavior.
> If the page does declare a specific activation event handler method the
> corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
> raised.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
