[
https://issues.apache.org/jira/browse/WICKET-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alastair Maw resolved WICKET-610.
---------------------------------
Resolution: Fixed
Fixed in r546685, at least for filter usage.
> header contributions fail on <error-pages>
> ------------------------------------------
>
> Key: WICKET-610
> URL: https://issues.apache.org/jira/browse/WICKET-610
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta1
> Reporter: Peter Ertl
> Assignee: Alastair Maw
> Fix For: 1.3.0-beta3
>
>
> if have the following in web.xml:
> <error-page>
> <error-code>404</error-code>
> <location>/404</location>
> </error-page>
> when I type in some intentionally stupid url like:
> http://localhost/myapp/non-existent-page
> the error page will properly show up...
> however, the header contributions contain wrong paths, e.g.:
> <wicket:link>
> <link rel="stylesheet" type="text/css" href="BasePage.css"></link>
> </wicket:link>
> will result in:
> <link href="404/resources/mysite.pages.BasePage/BasePage_de.css"
> rel="stylesheet" type="text/css"></link>
> however, this is wrong (path contains a "404/" ) as it should be:
> <link href="resources/mysite.pages.BasePage/BasePage_de.css"
> rel="stylesheet" type="text/css"></link>
> so, on error pages, resources are not usable because the error page path is
> appended at the beginning...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
