Johan Compagner wrote:
so we dont support this currently?
myserver1.xxx.com:80 -> localhost:8080/myapp1
myserver2.xxx.com:80 -> localhost:8080/myapp2
We support that just fine. That, in fact, is most of the reason why
we're using relative URLs in 1.3.
Murat: I have this working perfectly fine on lots of hosts.
What version of Apache do you have? Don't forget to add the
ProxyPassReverseCookiePath directive in, or you may have issues with
sessions.
It sounds to me like your Apache isn't honouring the ProxyPassReverse
directive.
Explanation
===========
When a request comes in to your Apache, it forwards it on using the
ProxyPass configuration to your tomcat/jetty/whatever.
If you're using a context path other than the root one, then that
request looks like this:
http://appserver:8080/contextPath/filterMapping/pageName
or
http://appserver:8080/contextPath/filterMapping/?wicket:interface=[...]
etc.
The appserver doesn't know anything about your proxy, so when it does a
302 redirect, it will do it to somewhere like this:
/contextPath/filterMapping/?wicket:interface=[...]
Apache is then responsible for converting the URL in the 302 redirect
into the proxied-version. It does this using the ProxyPassReverse
config. In the above example, it'll need to rewrite /contextPath/ to /
ProxyPassReverseCookiePath is used to do the same thing with any cookies
in the response. Cookies have a URL/domain, and your Tomcat will set
them at "/contextPath/", so that also needs rewriting to "/" otherwise
the browser won't send them on the next request, which means your
session won't work.
Murat: My suggestion to you is to strip out all the other config from
your VirtualHost (all the RewriteEngine stuff, etc.) and first get it
working using the basic set-up on the wiki-page. This does work.
Regards,
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
