[
https://issues.apache.org/jira/browse/WICKET-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alastair Maw resolved WICKET-219.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3
This is now sorted out "properly" in 1.3 using relative URLs.
TODO: port this to Wicket 2.0
> WicketFilter doesn't work with mod_proxy and setContextPath()
> -------------------------------------------------------------
>
> Key: WICKET-219
> URL: https://issues.apache.org/jira/browse/WICKET-219
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3, 2.0
> Reporter: Alastair Maw
> Assigned To: Alastair Maw
> Priority: Minor
> Fix For: 1.3
>
>
> If one sets up mod_proxy as here:
> http://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html (see "why
> this doesn't always work") isWicketRequest() in WicketFilter always returns
> false.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
