Mystery solved, I think. I did a little more digging around & discovered that my cookie had two JSESSIONID values. I didn't even know this was possible.
Neither of the values matched Tomcat's session id & the browser was unable to update the cookie's JSESSIONID properly (no surprise). I deleted this rogue cookie & all apears to be working as expected. Lots of moving parts ... -- Jonathan Rosenberg Founder & Executive Director Tabby's Place, a Cat Sanctuary http://www.tabbysplace.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
