You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/04/27 12:21:15 UTC

[jira] [Commented] (TAP5-2278) ModuleDispatcher returns start page for requests to nonexistent modules

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

Jochen Kemnade commented on TAP5-2278:
--------------------------------------

There's even a test that ensures the ModuleDispatcher "returns false if no module is found". So that actually seems to be the intended behavior. I wonder why, because AssetDispatcher behaves differently (i.e. sends a 404 status).

> ModuleDispatcher returns start page for requests to nonexistent modules
> -----------------------------------------------------------------------
>
>                 Key: TAP5-2278
>                 URL: https://issues.apache.org/jira/browse/TAP5-2278
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Jochen Kemnade
>
> A request to {code}${BASE_URL}/modules.gz/t5/core/xyz.js{code} returns the index page, it should return a HTTP 404 instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)