This isn't a PHP question in particular, and if you have any recommendations for a more appropriate community please let me know.
My problem has to do with the BACK button on browsers and POST data. Is there anyway to eliminate the "page has expired" messages?
Simplified example:
User comes to the site, sees PageA which has a login form.
After submitting Login info (method="POST"), they see PageB.
User browses to PageC.
User then presses back button to PageB, gets error message.
That was just a simple example. In this case it's pointless for the browser to try and resend the POST data because the user is already logged in.
Almost every page on my site uses POST because almost every page has data with a form for changing the data. After a user clicks submit, I update the database, and display the updated data. Since this page has other links on it, it is only natural for user to want to come back to it.
I realize I could create my own BACK button on my pages and keep track of things in a session variable, but it's kind of an ugly fix and users would be clicking on the wrong back button anyway.
Many websites don't seem to have this problem, so it seems I am missing something.
My problem has to do with the BACK button on browsers and POST data. Is there anyway to eliminate the "page has expired" messages?
Simplified example:
User comes to the site, sees PageA which has a login form.
After submitting Login info (method="POST"), they see PageB.
User browses to PageC.
User then presses back button to PageB, gets error message.
That was just a simple example. In this case it's pointless for the browser to try and resend the POST data because the user is already logged in.
Almost every page on my site uses POST because almost every page has data with a form for changing the data. After a user clicks submit, I update the database, and display the updated data. Since this page has other links on it, it is only natural for user to want to come back to it.
I realize I could create my own BACK button on my pages and keep track of things in a session variable, but it's kind of an ugly fix and users would be clicking on the wrong back button anyway.
Many websites don't seem to have this problem, so it seems I am missing something.
