David Cotter wrote:
This turns out to be because I call session.invalidate() and then
request.getSession(true). I don't have to do this so it's fine. Don't know
if two JSESSIONIDs is valid behaviour.
In the case of the sample quoted the new one will just overwrite it.
There are a few minor pro
This turns out to be because I call session.invalidate() and then
request.getSession(true). I don't have to do this so it's fine. Don't know
if two JSESSIONIDs is valid behaviour.
Regards,
David
On 9/1/06, David Cotter <[EMAIL PROTECTED]> wrote:
I send a request into my web app and the respons
I send a request into my web app and the response contains two JSESSIONID
cookies. This doesn't cause a problem on most browsers but on some OpernWave
mobile browsers the two identicle cookies seems to be cause the browser not
to return the cookie is subsequent request thereby dropping the session
