Hello all,
I've been having an interesting problem with dynamic session timeouts and the SecurePage skeleton provided by the examples. I've got a servlet hierarchy based on the SecurePage example to handle authentication. It generally works fine, but when the user leaves the session idle a long time, things can get weird. If the session gets flushed to disk, and then times out completely - and then the user sends another request, the session is restored from disk and the request is fullfilled. Then the NEXT request will be denied saying that their session has timed out.
Any ideas on where I should look, or what the source of this might be?
Thanks in advance,
Chris Backas


-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to