> Did you actually test it ? Rémy, I started two of my jsp applications. Logged into one, then accessed the other (which automatically signs me in because of the SingleSignOn.) Waited for one minute (my timeout interval), and the sessions expired without throwing any exceptions. Next, I logged in again under both applications (the same as before), but manually logged out by invalidating the session. Again, no exception were thrown. To be fair, I'm using Tomcat 4.1.27 with a few patches applied. I do not know how this would behave in Tomcat 5.0.
Hopefully Brian can take the patch I added, and test it under 5.0 since he indicated he was available to make the change. Luke > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED] > Sent: Monday, November 24, 2003 1:49 PM > To: Tomcat Developers List > Subject: Re: cvs commit: jakarta-tomcat- > catalina/catalina/src/share/org/apache/catalina/authenti cator > SingleSignOnEntry.java AuthenticatorBase.java BasicAuthenticator.java > DigestAuthenticator.java FormAuthenticator.java NonLoginAuthenticator.java > SSLAut > > Nelson, Luke wrote: > > > Brian, I believe I just fixed those issues. See the latest patch to > > 9077. > > Did you actually test it ? Your patch calls getLastModified, does this > really work if the session *did* timeout (and as such is no longer valid) > ? > > Rémy > > > > --------------------------------------------------------------------- > 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]
