Do you use container managed authentication? If so, where did you make this check?
My understanding is that the container will take control and send the user directly to the login page with a new session in place (in the same way as a new user login would). -Michelle -----Original Message----- From: Thinh Doan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 2:42 PM To: Struts Users Mailing List Subject: RE: Session Timeout? The way we did it was checking an object (e.g. user) in session. If it's null, do errors.add(ActionErrors.GLOBAL_ERROR, new ActionError("session.timeout")); (session.timeout is defined in your app resource properties) then return (mapping.findForward("logout")); this logout fwd will then go back to the login page with the time out message. Thinh -----Original Message----- From: Michelle Popovits [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 12:49 PM To: '[EMAIL PROTECTED]' Subject: Session Timeout? I have a struts web application which uses container managed authentication. When a user is logged into the application and the session times out, the next user-initiated action will result in the login page being displayed (the j2ee container makes this happen). How is it possible to tell that the reason that the user was directed to the login page was because the session timed out and not because it was the users first attempt at accessing the resource? I would like to display message to the user indicating that the reason they are in the login page is the result of a session timeout. I am currently constrained to use of the Servlet 2.2/JSP 1.1 spec. TIA, Michelle -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>