Hello, We are having a web app which uses session over both plain and SSL connections.
The very first time that someone accesses our initial page (i.e. never before visited the site so that there is no session cookie on his/her browser, not even an expired one) the server creates a session and sends the appropriate cookie to the browser. The problem is that for some reason the created session is destroyed immediately after the response for the page commits (i.e. after the page finishes loading). At this time, I have a cookie containing the JSESSIONID of an expired session. If I refresh the page or close and open later, etc. the request to the server contains the cookie sent initially and of course, since the server expired the session it sends back a new JSESSIONID. This time, the second one, the server does not expire the session. My question is: what is causing the session to expire the very first time since it has just been created and why is this fixed on subsequent requests? What can I do so that when a session is instantiated it is maintained? Please note that I experience exactly the same behaviour the very first time I access a page over SSL. Thanks in advance for your help. Rgds, Michael --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
