[
https://issues.apache.org/jira/browse/WICKET-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137175#comment-13137175
]
Anatoly Kupriyanov commented on WICKET-4168:
--------------------------------------------
Are you sure? Just tried it with JBossAS7 and Tomcat 7.0.22. Fails everywhere.
I suspect you have deployed it on ROOT once, and "../../" works.
As I see, the problem is in the getClientUrl method. If it's normal page it
uses the private method "getUrl", and it does remove context and filter paths,
but for an error page it doesn't. Hence all resource relative urls have extra 2
levels up "../../".
> Error page resource relative urls are wrong
> -------------------------------------------
>
> Key: WICKET-4168
> URL: https://issues.apache.org/jira/browse/WICKET-4168
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.2
> Reporter: Anatoly Kupriyanov
> Assignee: Pedro Santos
> Attachments: myproject.zip
>
>
> The wicket page exposed as 404 error page has wrong links to resources. The
> sample project is attached.
> Run the project with "mvn jetty:run" and go to url
> "http://localhost:8080/bug/404"; - it's mapped wicket page, works perfect. But
> if you type any wrong url such as "http://localhost:8080/bug/aaaaaa"; the page
> doesn't have styles and images.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
