There is an option in the IE config about reusing windows. This option controls if each window has it's own cookies separate from other open windows. This is sometimes useful to a developer, they can be running multiple sessions, with potentially different logins at the same time.
-----Original Message----- From: Paul Wallace [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 7:26 PM To: Tomcat Developers List Subject: RE: window close session invalidate -----Original Message----- From: Paul Wallace Sent: Thursday, 7 August 2003 9:20 AM To: Tomcat Developers List Subject: RE: window close session invalidate OK, Thanks for that. An interesting note however..after some testing, the session is not killed when run from another terminal i.e running the same instance of TC (same server) but from different terminals. That would suggest it is an IE configuration issue (at much annoyance to certain developers). I will at this stage bring this up on the user list! Thanks Paul. i had the same problem with internet explorer. mozilla seems to work properly. i tracked the problem down and found out that internet explorer looses the session cookie when closing the popup browser window. then i added <DefaultContext cookies="false" /> to my virtualhost definition in server.xml to disable the session-cookie mechanism. after that everything worked fine for me. remember to encode all urls with response.encodeURL(). jochen schwörer Wednesday, August 6, 2003, 6:00:57 AM, you wrote: PW> Dear all, PW> May someone enlighten me on why my session is being invalidated PW> when I close a browser window? I am doing this in one of two ways - the PW> application close icon on the top right of the window, or a simple: PW> <a href="javascript:window.close();">CLOSE</a> PW> Does anyone have any experience of this? The session is being killed and PW> thus so is my app. I will submit this query to the user list, but PW> thought it appropriate for this list as I am getting the same result PW> from multiple instances of TC on different servers, implying it is not a PW> configuration issue as first suspected. PW> Thanks PW> Paul. PW> --------------------------------------------------------------------- PW> To unsubscribe, e-mail: [EMAIL PROTECTED] PW> For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]