Peter Rossbach wrote:
Next Information,
I have analyse the traffic between Browser and Tomcat 5.0.24 (tcpmon)and the
see following:
cookie= JSESSIONID=1097F923FE5514A29042ABAC28E01CB8.node2; nde-textsize=13px
So you mean this is the value of the "cookie" header ? There's nothing wrong with that.
other thing is, that I see more than one JSESSIONID Cookie for the admin application.
With 5.0.22 I can't reproduce this behaviour.
There are cases where there can be more than one session cookie (TC will now use the first one which is valid). Again, nothing wrong.
I did some research of the changes between 5.0.22 and 5.0.24:
- the 408 means the session has been lost for some reason
- the session id parsing code has been modified, but is, as far as I can tell, equivalent to the previous code (it is a cut and paste of the block which was previously responsible for session id cookie parsing)
- the cookie handling code has been modified as well, but this doesn't seem relevant
- the session code is unchanged (and session tracking works fine for me from what I can see)
Can you give more details ? (I can't believe how much weird problems you always seem to run into)
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
