[
https://issues.apache.org/jira/browse/WICKET-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael Winterhalter updated WICKET-5355:
----------------------------------------
Description:
When I receive a request to my application as for example:
http://localhost:8080// Wicket misinterprets the double slash // in the end.
I have a custom error page installed. This page works fine with any page,
independent of the Instead of resolving links relatively to the resource "/",
it treats the request as if http://localhost:8080/ was requested. As a result,
all links and external resources are resolved wrong and result in 404s.
If the first argument is named as in http://localhost:8080/a// the double slash
is interpreted right.
was:
When I receive a request to my application as for example:
http://localhost:8080// Wicket misinterprets the double slash // in the end.
I have a custom error page installed. This page works fine with any page,
independent of the Instead of resolving links relatively to the resource "/",
it treats the request as if http://localhost:8080/ was requested. As a result,
all links and external resources are resolved wrong.
If the first argument is named as in http://localhost:8080/a// the double slash
is interpreted right.
> Wrong interpretation of double slash as the first pre-filter context value of
> a request URL
> -------------------------------------------------------------------------------------------
>
> Key: WICKET-5355
> URL: https://issues.apache.org/jira/browse/WICKET-5355
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.8.0
> Reporter: Rafael Winterhalter
>
> When I receive a request to my application as for example:
> http://localhost:8080// Wicket misinterprets the double slash // in the end.
> I have a custom error page installed. This page works fine with any page,
> independent of the Instead of resolving links relatively to the resource "/",
> it treats the request as if http://localhost:8080/ was requested. As a
> result, all links and external resources are resolved wrong and result in
> 404s.
> If the first argument is named as in http://localhost:8080/a// the double
> slash is interpreted right.
--
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
