On Thu, Jun 19, 2008 at 6:09 PM, André Warnier <[EMAIL PROTECTED]> wrote: > > > So now that it is settled that different names for the cookies /would/ solve > the problem, is that a possibility in Tomcat ? > Is it possible for one application to "influence" the name of it's session > cookie, so that we could have JSESSIONID-1 and JSESSIONID-2 ?
Errm, no :-) As far as I know there is no chance to change the cookie name since its part of the spec and hardcoded. But, you can change the path of the cookie to be the same as the webapp name, in fact it already is. So if you have the webapp1 and webapp2 than both can have a JSESSIONID cookie with according path (webapp1 and webapp2). If the browser access webapp1 it sends only the JSESSIONID cookie with webapp1 in path and when it accesses webapp2 it sends the webapp2 cookie. Herewith each of your webapps has its own session and its own session cookie. Right now i have 7 JSESSIONID cookies in my FFox, with 2 of them issued by localhost, one by app sshop and one by app bouncer. Both apps act independently and have own sessions, even in same tomcat. The problem that OP has can only occure if both he's webapps have the same name (or no name -> ROOT), hence overwriting each other. In that case rename or force one of them to use rewriting. regards Leon --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
