That is a handy article, but it doesn't address the underlying problem.
What I have done in the past is this:
Post your page to whatever page you wish to have handle the database update, but then on successful completion redirect to another page, or even to the same page, it doesn't matter. By redirecting, you are getting the browser away from a page that was posted to. You may need to "carry over" something, like a message indicating that the operation was completed, but this is much easier than trying to block all the different ways the user can go "back". They can refresh that "your record is updated" page over and over without affecting the actual db operation.
Peter
------------------------------------------------------
Work smarter, not harder.
|