[
https://issues.apache.org/jira/browse/WICKET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475152
]
Jean-Baptiste Quenot commented on WICKET-294:
---------------------------------------------
This URL gives a 404:
http://localhost:8080/wicket-examples/niceurl/my/mounted/Xpackage
But you're right this one gives a 500:
http://localhost:8080/wicket-examples/niceurl/my/mounted/packageXXX
I suspect that the code uses something like startsWith(mountPath)
> WebRequestCodingStrategy: path mounting and matching
> ----------------------------------------------------
>
> Key: WICKET-294
> URL: https://issues.apache.org/jira/browse/WICKET-294
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3, 2.0
> Reporter: Stephane Bailliez
>
> Assuming a mount path to "/p", it will match /pxyz
> Assuming this is the desired behavior of matching (warning), then to avoid
> this match it should be declared "/p/" but it will create urls such as
> '/app/p//SomePage'. which is wrong.
> In the servlet specs, the mapping syntax '/p' is an exact match, this is not
> what you want in your case since you're doing path mapping, so the syntax if
> you want to stick close to the servlet specs should be '/p/*' or if you wan
> to get close to mod_proxy syntax it would be '/p/'
> Note that the examples are also using this wrong mapping declaration. In the
> example below: both should throw a 404:
> http://www.wicket-library.com/wicket-examples/niceurl/my/mounted/packageXXX
> http://www.wicket-library.com/wicket-examples/niceurl/my/mounted/Xpackage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
