I’m developing ASP.NET applications and stuck with a “problem” relating to resubmit behaviour.
I’m controling the re-submit using a counter in form submit event which disables the submit if it’s already been posted.
My application is a 3 step workflow and when the 3rd step is shown the transaction was submited from step2 to step 3.
What’s my problem? Well… i want to avoid the user to resubmit the data by pressing the F5 or all other possibility. I don’t want to disable the key because may be workarounds.
I’m wondering if i can remove the post data in a HTTP module that runs after the render was completed and right before the response is sent to the user.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
You can use Post/Redirect/Get “pattern”, where when user post data, you redirect it (after processing submitted data) to another page that will response to get. Just like stackoverflow and another sites are doing.
Here’s is the Wikipedia page that explains the Post/Redirect/Get Pattern.
Method 2
Maybe I misunderstood your question/issue but it sounds like you may be making things harder than they have to be. If you are already keeping track of whether or not the form has been submitted before, why cant you just check that flag on the code behind before performing whatever logic you execute on the submit? If it has already been submitted before, just ignore the resubmit event and maybe set an error message.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0