Basically you would have to capture the back button, send a message to the server (your call to the action class), and then let the browser process the back button request. This usually just results in the previous page in history being loaded from cache, which is why the server doesn't know that the back button was used.
Philip Shanks, SCJP - Castro Valley, CA
My boss never outsources or has lay-offs, and He's always hiring. I work for Jesus! Prepare your resume!
We have written a Filter that will add to the response's header so that in theory none of our pages should be cached by any server or browswer. Therefore when a browsers back button is pressed a new request is sent to the server for the page.
Joined: Oct 15, 2002
Originally posted by Eric Pascarello: There is no action fired for the back button.
On the other hand, wouldn't the onunload event get fired as a result of a back-button click? Perhaps this could somehow be leveraged to alert the application that the back button *may* have been used. I don't know how this could be made either efficient or effective. [ February 09, 2007: Message edited by: Philip Shanks ]