Chris,
Thanks for your prompt reply.
My apologies - I was getting confused. The browser had already assigned a
jsessionid through a cookie just by viewing the login page, so from them on
anything I passed on the URL was being ignored.
Thanks for your time,
Richard.
--
View this message in co
Torsten,
Thank you for the quick reply. My apologies: I was getting confused.
I now realise sending jsessionid on the URL gets ignored if there is already
a jsessionid in the cookie, which there will be if you have even briefly
touched the site in any way (eg. to pull up the login page).
Thanks
Dear All,
When passing a jsessionid on the URL such as...
http://foo.com;jsessionid=123
...does Tomcat do something clever, like checking the User-Agent, before
agreeing to hook into the existing '123' session?
If I log in using, say, Firefox and note the jsessionid, then open a new
Firefox