I'm seeing what I think is odd behavior regarding jsessionid's.
[My setup(s): Tomcat 6.0.20 on a MacBook Pro using Java 1.6.0_17,
Tomcat 6.0.18 on CentOS 5 using Java 1.6.0_12 ]
I'm seeing the same behavior on both systems, and the same
behavior happens with Safari and FF. Both browsers have
On 04/01/2010 20:52, Ken Bowen wrote:
I'm seeing what I think is odd behavior regarding jsessionid's.
[My setup(s): Tomcat 6.0.20 on a MacBook Pro using Java 1.6.0_17,
Tomcat 6.0.18 on CentOS 5 using Java 1.6.0_12 ]
I'm seeing the same behavior on both systems, and the same
behavior happens
I'm not sure about that. Here's what seems to me to be the sequence
of events:
Browser sends initial request http://myapp.com
Tomcat creates session and generates page for this request.
Tomcat doesn't know that Browser supports cookies, so it
should append jsessionid (but
On 04/01/2010 21:43, Ken Bowen wrote:
I'm not sure about that.
Run through your test again, but this time:
a) look at the html source of the responses and/or look at the URLs for
the links you are clicking on before you click on them.
Here's what seems to me to be the sequence of
events:
Thanks Mark. That cleared it up for me:
Re: a) look at the html source of the responses and/or look at the
URLs for
the links you are clicking on before you click on them.
That's the trick. The source for that (in a JSP) looks like:
a href= %=response.encodeURL ( anotherPage.jsp )%
