Best Practice with Browser navigation buttons

Question

My Web Ap does a secured login and then the user is
guided to various pages via Command buttons and links.
The question I have is if the user presses the browser buttons to
go back the various prior screens appear with waht the user
entered. I do ot want this.
What is the best practice to stop this functionality and or capture a event
that f the user does this the screens are cleared?

Answer 1

(I believe all Faces page navigation is done via POST (command{Button,Link}).)
In our app (pre-Faces, but now we're moving to Faces, and I just can't tell you how much fun it is grafting Faces onto an old JSP/servlet app), we chose to open a new window when the user logs in, without browser decorations (i.e., navigation buttons). (This is done via javascript window.open(), with the appropriate options.)
The old window can't be closed due to Javascript security constraints, so we redirect it to another page so the user won't be confused if he or she stumbles across what looks like a login page (by exposing that old window).
After that, it's mostly an effort in user education: we just don't tell them about things like alt-left-arrow to go back or F5 to refresh or right-click anything (except View Source when we're debugging a problem). If they're "smart", we tell them "Don't do that", where "that" is either "stick your finger in your eye" or "use alt-left-arrow", depending on your sense of humor and ability to parse my idiomatic English.
[There's an old joke in which a man goes to a doctor and says "Doctor, my eye hurts".  The doctor says "Hmm, can you tell me more?"  The patient says "Yes, it hurts when I do [i]this," and proceeds to jab his finger into his eye. The doctor says, "Ah, I see. Well, don't that any more," and the patient walks away satisfied with his "cure."]
John.