Why can the JSESSIONID name not be changed?
- From: brycenesbitt <bryce1 (at) obviously.com>
- Date: Tue, 5 Dec 2006 20:52:28 -0800 (PST)
Christopher Schultz-2 wrote:
>
> And why only in MSIE?
>
> Stefan also needs to understand that these cookies also have "paths"
> encoded into them, so that that do not interfere (as long as the paths
> themselves do not interfere).
>
> - -chris
>
MSIE processes the "paths" differently than Gecko based browsers.
MSIE returns the a less specifc session cookie first. All the other
browsers return the most specific cookie first.
Two webapps CAN interfere with each other, under MSIE:
See:
http://www.obviously.com/tech_tips/jsessionid_msie.html
--
View this message in context: http://www.nabble.com/Why-can-the-JSESSIONID-name-not-be-changed--tf532684.html#a7713586
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users (at) tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe (at) tomcat.apache.org
For additional commands, e-mail: users-help (at) tomcat.apache.org