I see this same behavior with our application. Apparently nothing to worry about.
Raphael Jean EntropySoft > -----Original Message----- > From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of > Andreas Bulling > Sent: samedi 25 mars 2006 14:14 > To: Tapestry users > Subject: Re: JSESSIONID and cookie > > On 25. Mär 2006 - 13:09:59, Martin Strand wrote: > | 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. > > Thanks for your answer, sounds logical! ;) > That means this is normal behaviour? Could someone please confirm this? > > --------------------------------------------------------------------- > 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]
