FYI, I'm not concerned about the form resubmitting to the database - it won't allow duplicate data. Instead, the user gets sent to a page saying "this has already been submitted". This page has a top menu and a side menu for the site, plus I could add a "click here to continue" link or button. Is that enough?
My concern is that the users of this particular site tend to be older and less computer savvy and a few might be frustrated by their browser not taking them back to the form. Am I worried about nothing here?
I've tried a few approaches to resolving this (redirecting user to the form again would be my ideal solution) but I'm confounded. Here's the setup :
form.html submits to processor.asp on windows server
processor.asp submits to processor2.php on linux server
processor2.php redirects to success.html on windows server, or if data has already been submitted it redirects to fail.html on windows server
Another confounding factor - some browsers throw their own warning when trying to use the back button - example: "As a security precaution, Firefox does not automatically re-request sensitive documents."
Besides the website's older user experience, I am also trying to use this 2 server system for an internal use where the user would definitely want to get back to the form to submit different data. The windows server is mine, but the database must be fed from the linux server, which I have limited access to. I can add to the php script, but I'm not good with php. These internal users can learn to use a link to get back, but I'm sure some of them are also addicted to the back button.
Thanks for any input.