Hi Jan, Have you tried proxying with AJP instead of HTTP? Some of this complexity goes away then.
Using mod_rewrite's [P] flag to proxy requests shouldn't be incompatible with ProxyPassReverse or ProxyPassReverseCookieDomain. Did you try it? Dan On Fri, Jun 1, 2012 at 2:51 AM, Jan Riehn <jan.ri...@1und1.de> wrote: > Hello, > > we use a tomcat behind a apache. we also use mod_rewrite proxy rules to > manage requests from the apache to the tomcat. Our wicket application > modifies the location header: > > curl -I > http://wicket-application/**application-context/login<http://wicket-application/application-context/login> > > HTTP/1.1 302 Moved Temporarily > Date: Wed, 30 May 2012 13:45:15 GMT > Server: Apache-Coyote/1.1 > Expires: Thu, 01 Jan 1970 00:00:00 GMT > Pragma: no-cache > Cache-Control: no-cache, no-store > Location: > http://localhost:8080/**application-context/login<http://localhost:8080/application-context/login> > Set-Cookie: JSESSIONID=**5F08FEDBAAABD7F3E83C7EF785C6A6**88; > Path=/application-context > Vary: User-Agent > Content-Type: text/plain > > > So we get a redirect to localhost. the hint: https://cwiki.apache.org/** > WICKET/wicket-application-**behind-modproxyhttp-and-https.**html<https://cwiki.apache.org/WICKET/wicket-application-behind-modproxyhttp-and-https.html>does > not work, because we are using rewrite maps for our mod_rewrite proxy > rules. So we have no chance to use ReverseProxy. > > How can I solve this issue? > > Best regards, > > Jan >
