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 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 between requests. Perhaps this is a known issue. My application has a few filters that the request passes through before getting to a servlet and these filters are crerating or accessing the session. <HTTP-raw> HTTP/1.1 200 OK <HTTP-raw> Server: Apache-Coyote/1.1 <HTTP-raw> Set-Cookie: JSESSIONID=C90DF7930FFFFE158150140E41FB2FAC; Path=/globalen <HTTP-raw> Set-Cookie: tbs_identity=88881043786:3032; Expires=Sun, 01-Oct-2006 15:51:23 GMT; Path=/globalen <HTTP-raw> Set-Cookie: JSESSIONID=F974FDF3E26ACF12203F9F2C190735DA; Path=/globalen <HTTP-raw> Date: Fri, 01 Sep 2006 15:51:23 GMT <HTTP-raw> Connection: close <HTTP-raw> Cache-Control: no-cache <HTTP-raw> Pragma: no-cache <HTTP-raw> Content-Type: text/html;charset=ISO-8859-1 <HTTP-raw> Transfer-Encoding: chunked Would appreciate any help on this - in the meantime I will try to find the issue trhough elimination. Regards, David
