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 to be forwarded to MyApp in Tomcat.
So, I fired up mod_proxy and included the following rules:
ProxyPass / ajp://localhost:8009/MyApp/
ProxyPassReverse / [***]ajp://localhost:8009/MyApp/
That works, with the following disadvantages:
- there's *always* a jsessionId parameter attached to the URL (not only
on the first request), why?
- Wicket is opening a new session for *every* request to resources
(images, js, css) that are loaded on the pages (I guess because they
don't have access to the jsessionId)
- if I remove the jsessionId parameter from the URL in the browser, my
(Wicket) session is gone (logged in user is logged out) and Wicket
starts a new session
If I configure mod_proxy in that way:
ProxyPass /MyApp ajp://localhost:8009/MyApp
ProxyPassReverse /MyApp [***]ajp://localhost:8009/MyApp
... then everything is fine, no more jsessionIds (only on first
request), no more new sessions for every resource, just like it should
be. But I need MyApp to be accessible from www.mydomain.com ...
I don't get the point for that behavior, could someone enlighten me maybe?
P.S.:
yes, I need Apache and mod_proxy, because there are several paths that
are excluded from proxing, that point to other resources on that server,
e.g.:
ProxyPass /images !
So, running Tomcat only (on port 80) without Apache2 does not seem an
option to me.
Cheers,
-Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
