> From: Jose María Zaragoza [mailto:demablo...@gmail.com] > Subject: Re: Multiple JSESSIONID cookies being presented.
> > Thanks for the clarification of what's supposed to happen on receipt, Jose. > > However, I am describing what happens on first contact from the client to > > the server. > > The browser sends https://hostname/APP2, and Tomcat returns: > > JSESSIONID=XXXX, path=/ and JSESSIONID=YYYY, path=/APP2/ > Indeed, it doesn't make sense for me to return different id ( XXXX , > YYYY ) if you are accesing to only one context (/APP2) > Are you sure that your webapp deployed in /APP2 is not accesing to > resources ( session-aware resources as JSP, servlet, .. .I mean) > stored in ROOT context ? As I think someone previously mentioned, the client (browser) may well be sending an unsolicited request to the default webapp, such as when trying to retrieve favicon.ico. You might want to run Fiddler or Wireshark on the client to see exactly what's being sent to the server. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
