Thomas Götz wrote:
- there's *always* a jsessionId parameter attached to the URL (not only
on the first request), why?
Ok, problem seems solved, adding a ProxyPassReverseCookiePath directive
did the trick.
Cheers,
-Tom
--
Isammoc OFF wrote:
So, running Tomcat only (on port 80) without Apache2 does not seem an option to
me.
What about using mod_jk ?
Well, what stands against mod_proxy? It seems to be working for me as
described earlier. I only have problems with it when I try to forward
'/' via ProxyPass. B
> So, running Tomcat only (on port 80) without Apache2 does not seem an option
> to me.
What about using mod_jk ?
http://tomcat.apache.org/connectors-doc/
http://tomcat.apache.org/tomcat-3.3-doc/mod_jk-howto.html
--
Isammoc
-
Hi there!
I have the following setup:
- an Apache httpd (2.0.x), running on port 80
- a Tomcat (6.x) running on port 8080
The Wicket webapp MyApp is running in Tomcat as the only webapp on that
server. I have a registered domain www.mydomain.com, so I want
everything hitting www.mydomain.com
