Cc: 'Tomcat Users List '
Subject: getting desperate here :)
Hello all,
i have sent this one before, but i am hoping someone else has
had this particular problem.
__
i am hoping someone has seen the following behavior.
TomcatA sends a redirect to TomcatB
Hello all,
i have sent this one before, but i am hoping someone else has
had this particular problem.
__
i am hoping someone has seen the following behavior.
TomcatA sends a redirect to TomcatB
on the backend, I can see that TomcatB receives a JSESSIONID that was
Hi,
Are you invalidating the session from TomcatA before you redirect to TomcatB?,
even a redirect should be able to clear the session cookie if you've
invalidated the session.
We do much the same thing sometimes and don't have this problem, the
session.invalidate seems to be the only thing
http://www.yoavshapira.com
-Original Message-
From: Alex Korneyev [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 02, 2004 10:06 AM
Cc: 'Tomcat Users List '
Subject: getting desperate here :)
Hello all,
i have sent this one before, but i am hoping someone else has
had
makes it work by coincidence), whereas IE just seems to suck it
all up as one JSESSIONID.
HIH,
Al G
- Original Message -
From: Alex Korneyev [EMAIL PROTECTED]
Date: Thursday, December 2, 2004 9:05 am
Subject: getting desperate here :)
Hello all,
i have sent this one before
Hello Peter Mengell,
can you please clarify what you mean by session.invalidate
alex korneyev
Thursday, December 2, 2004, 9:13:44 AM, you wrote:
Hi,
Are you invalidating the session from TomcatA before you redirect to TomcatB?,
even a redirect should be able to clear the
From the servlet API:
Invalidates this session then unbinds any objects bound to it.
If a browser's TomcatA session is invalidated and they return to
TomcatA, TomcatA will issue a new session ID to the browser. The session
ID represented in the cookie would no longer correspond to a know
