I don't know for sure, but I think this is what's going on:
When the session is first created, a cookie is set and JSESSIONID is
appended to all links. If your browser doesn't send back the cookie, the
JSESSIONID will continue being appended to all links. If your browser
accepts the cookie and sends it back on the next request, the cookie will
be used instead to track the session id.
Initially, there's no way for the server to know whether your browser
accepts cookies or not, so it tries both.
Martin
On Sat, 25 Mar 2006 11:42:42 +0100, Andreas Bulling
<[EMAIL PROTECTED]> wrote:
Hi all,
just a short question - I will see if the answer will also be that short,
as I have no clue what's going wrong here I don't know... :(
After logging in into my plattform (built with Tapestry) a JSESSIONID
is appended to all links to the different subpages. But:
As I can see a cookie is also created with the same JSESSIONID.
From my understanding either a JSESSIONID _or_ a cookie is used
to track the current session, isn't it? Why do I have both, any idea?
The second strange thing is that after clicking on one of the
links the JSESSIONID isn't appended to the links anymore?!
Thanks for your help!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
