Ron McNulty wrote: > The only fix was to correctly configure the offending server - there is > nothing Tomcat can do. When a browser has two cookies with the same name > in scope, the outcome is indeterminate. We found that the wider scoped > cookie took precedence. I've often thought the name of the JSESSIONID > cookie should be configurable, but to my knowledge it is hard-coded.
As of 6.0.19 it is configurable. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
