Tim, Thanks for your most informative response. Unfortunately, the two cookies I am observing are from the same webapp.
Would it have something to do with the requests to www.mydomain.com and mydomain.com? I see such difference for at least one of the requests for those sessions. My app hardcodes www.mydomain.com links. I remember I had some problems with enabling https, whereby I would loose session going back and forth between https and http due to higher priorities elsewhere. I still have not solved that, but remember reading something about declaring the cookie domain in Tomcat configuration (why not webapp?). I also forgot to mention that I have Cocoon 2.0.4 installed for the web app, but since it had a broken JSPGenerator, I did not use it to process JSP pages, only to direct requests for now. Ed > It is valid to have multiple JSESSIONID cookies. Because each webapp has its > own session id. So if you have a webapp mapped to / and a webapp mapped to > /cowbell. You will have 2 JSESSIONID cookies. One for path / and one for path > /cowbell. The cookie RFC says that cookies of the same name should be sent > from most specific to least specific. > > So you might be observing this behavior. And some patch revisions of IE don't > obey the cookie order rule. > > -Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
