Arvind Srinivasan wrote:
Hi,
In Tomcat 5.x and 6.x, the JSESSIONID Set-Cookie header is added to the
response during session creation (in Request.doGetSession), whereas in
Tomcat 4.x this used to be done during Response.sendHeaders(). Not that
it causes any problems, but TC 5.x/6.x responses can contain JSESSIONID
Set-Cookie headers even when there is no session or can contain multiple
JSESSIONID Set-Cookie headers (examples at the end of this mail)
Was there a problem in TC4.x when the JSESSIONID cookie was added when
the response headers were committed and hence this logic had to be moved
to Request.doGetSession in TC5.x/6.x?
This is not that easy to do. While it doesn't really support your
(funny) use case, the current impl is far simpler, so I would be in
favor of keeping it.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
