Troubleshooting HTTP 408 errors
https://access.redhat.com/kb/docs/DOC-52942 HTTP 408 error after a session timout on the login page Article ID: 52942 - Created on: Aug 25, 2009 10:36 AM - Last Modified: Mar 28, 2011 11:30 AM Issue With FORM based authentication, when users park on the login.jsp page for some time, they receive a 408 error telling them that the session has timed out when they input their credentials to submit the form to the j_security_check page. The 408 error is happening in IE 7. In Firefox, the following error text is shown, along with a warning symbol: "The connection was reset The connection to the server was reset while the page was loading. * The site could be temporarily unavailable or too busy. Try again in a few moments. * If you are unable to load any pages, check your computer's network connection. * If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web." Is there an easy and/or elegant way to intercept this error and create a new jsession? Environment JBoss Enterprise Application Platform (EAP) 4.x JBoss Enterprise Portal Platform (EPP) 4.x Resolution If the value for the web application is rather short, it could be increased in order to have this issue showing up less frequently. But it could still happen if the login page is left idle for longer than the defined timeout. The only way to work around this is to keep the session alive on the login page. This could be done with a small javascript function that periodically issues a request to the server to prevent the session from expiring. Root Cause The login will fail if the session associated with the request has expired. Diagnostics Uncomment RequestDumperValve to check the request/response content Check values in web.xml files