You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2013/02/10 22:49:13 UTC
[jira] [Closed] (TAP5-879) 404 is never raised automatically if the
application has an index page.
[ https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Massimo Lusetti closed TAP5-879.
--------------------------------
Resolution: Won't Fix
A new issue has been created to reflect what I would like to achieve.
Here we are talking only about Index pages and I want all pages to behave the same so I ask you to follow TAP5-2070 which will implement this plus more.
I you feel strong about this particular issue, please reopen.
> 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
> Assignee: Massimo Lusetti
> Attachments: TAP5-879.txt, TAP5-986.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira