Hi,
just to give some people a hint when facing the same problem like we did
with dynamic CSS/JS resources that are not requested with
JSESSIONID/Cookie and therefore are not routed to the correct server in
a clustered tomcat/apache environment with sticky sessions.
The reason in our environment for the above problem was:
Apache rewrote the webapp to reside in the root path of the domain, the
webapp however was deployed to the tomcats under their default path,
which is the name of the war file. The Session Cookie is created by
Tomcat and he sets the cookie path to /{Webappname}.
If your Apache doesn't rewrite the path inside the cookie, your page
gets delivered to the browser with links to CSS resources under root
path. The cookie path value however contains the webapp name.
The browser now sends only cookies along with requests starting with the
cookie path and in our case this resulted in css requests with
cookies/jessionid.
Now you have 3 different solutions to this problem:
1. Configure Apache to also rewrite your cookie path to "/"
2. Use the emptySessionPath="true" switch in the server.xml of tomcat.
See http://tomcat.apache.org/tomcat-5.5-doc/config/http.html.
3. Install the webapp under root of tomcat, not under the default
/warfile-name
A similiar problem with glassfish was already posted to this list:
http://wicket-users.markmail.org/search/?q=glassfish%20cookie#query:glassfish%20cookie+page:1+mid:o6t2php5xxn5qah7+state:results
Hope this helps someone else ;-)
Greets and thanks,
Chris Wewerka
http://threedimensions.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
