On 4/28/07, David <[EMAIL PROTECTED]> wrote:
Rashmi,
Thanks for your initial response. I guess I wasn't clear on a few things.
The behavior I'm seeing is the same in both Tomcat 5.0 and 5.5, and they are
both configured the same -- using default behavior for cookies.
Sorry for repeating this, but just to be clear, in the above
statement, default behavior means that cookies="true".
This means that in the browser when cookies are enabled, JSESSION id
will be written to a cookie.
I should elaborate further and mention that the urlEncode method causes url
rewriting to occur. So a cookie does not appear in my client browser
(verified with a cookie viewer for IE). Despite this apparent lack of
client side cookie, when doGet is invoked in step 3) Tomcat exposes a cookie
object with the session id of Session1 off of the HttpServletRequest object
What happens if you set cookies="false" ?
and has stripped off the Session 2 session id on the encoded URL from step
2).
David
-Regards
Rashmi
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
