tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-879) 404 is never raised automatically if the application has an index page.
Date Thu, 08 Oct 2009 18:15:31 GMT

    [ https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763603#action_12763603
] 

Thiago H. de Paula Figueiredo commented on TAP5-879:
----------------------------------------------------

Using an activation context or not is something that is decided per page, so a strict check
configuration could only affect Index pages (or even only the top one). We can easily create
a mixin that sends a 404 response when the activation context at least one parameter.

> 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.


Mime
View raw message