Alejandro Scandroli: +1 (non-binding)
On Sun, Feb 10, 2013 at 11:18 PM, Massimo Lusetti <[email protected]> wrote: > Hi devs, > this ia vote to introduce a new behavior on how Tapestry5 handle incoming > requests. > > The issue you should look at is: > https://issues.apache.org/jira/browse/TAP5-2070 > > Basically the proposal is to introduce new logic to respond with HTTP 404 > code to requests on unknown URL. > The concept of activation context within Tapestry5 has introduced a pretty > cool mechanism to control and format URL practically in any way the > developers need, but also has lead to serving requests to URL which are not > what the developers might want. > > For example a page named Super with an activation context as a String will > serve requests for: > > /super/mario > /super/luigi > > and so on, and this is wanted. But also will server requests for: > > /super/mario/luigi > > simply ignoring "luigi" ... In fact you can write as many paths as you want > in your URL. > > The proposed patch is disabled by default which cause the old and current > behavior, it can be enabled by a configuration symbol. > > I think the same rules as a vote for a release apply here. > > Massimo Lusetti: +1 (binding) > > -- > Massimo On Sun, Feb 10, 2013 at 11:18 PM, Massimo Lusetti <[email protected]> wrote: > Hi devs, > this ia vote to introduce a new behavior on how Tapestry5 handle incoming > requests. > > The issue you should look at is: > https://issues.apache.org/jira/browse/TAP5-2070 > > Basically the proposal is to introduce new logic to respond with HTTP 404 > code to requests on unknown URL. > The concept of activation context within Tapestry5 has introduced a pretty > cool mechanism to control and format URL practically in any way the > developers need, but also has lead to serving requests to URL which are not > what the developers might want. > > For example a page named Super with an activation context as a String will > serve requests for: > > /super/mario > /super/luigi > > and so on, and this is wanted. But also will server requests for: > > /super/mario/luigi > > simply ignoring "luigi" ... In fact you can write as many paths as you want > in your URL. > > The proposed patch is disabled by default which cause the old and current > behavior, it can be enabled by a configuration symbol. > > I think the same rules as a vote for a release apply here. > > Massimo Lusetti: +1 (binding) > > -- > Massimo On Sun, Feb 10, 2013 at 11:18 PM, Massimo Lusetti <[email protected]> wrote: > Hi devs, > this ia vote to introduce a new behavior on how Tapestry5 handle incoming > requests. > > The issue you should look at is: > https://issues.apache.org/jira/browse/TAP5-2070 > > Basically the proposal is to introduce new logic to respond with HTTP 404 > code to requests on unknown URL. > The concept of activation context within Tapestry5 has introduced a pretty > cool mechanism to control and format URL practically in any way the > developers need, but also has lead to serving requests to URL which are not > what the developers might want. > > For example a page named Super with an activation context as a String will > serve requests for: > > /super/mario > /super/luigi > > and so on, and this is wanted. But also will server requests for: > > /super/mario/luigi > > simply ignoring "luigi" ... In fact you can write as many paths as you want > in your URL. > > The proposed patch is disabled by default which cause the old and current > behavior, it can be enabled by a configuration symbol. > > I think the same rules as a vote for a release apply here. > > Massimo Lusetti: +1 (binding) > > -- > Massimo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
