If you have a custom error page set up you can trap the 408 response
code and redirect to an appropriate resource. Works for me :)
Alternatively, you can set up a meta refresh on your login page so you
never get the 408. Of course, because the refresh has to go to some
protected page and not b
I'm dealing with a problem where if a user hits a secured page and is
forwarded to a login page (using Form Auth). If the user sits on that login
page for too long, and then try to login they are confronted with a nasty
HTTP 408 error. I don't know if this behaviour is part of the servlet spec,
