sboux
asked on
Preventing multiple form submissions.
Hello everyone,
I am just curious can be done to prevent a client from jamming away on a submit button on a webform?
I have been googling away for a few alternatives but most articles and suggestions I have found involve javascript. Such as http://dotnetjunkies.com/WebLog/mjordan/archive/2004/02/17/7393.aspx. Although this is a terrific solution, it doesn't prevent anyone from being a shyster and disabling javascript and abusing a webform. This can especially be a pain when the form submission involves inserting into a DB. The result being multiple rows inserted.
So there has be some sort of server side solution where if javascript is disabled the multiple form submissions can be ignored or prevented.
My current idea is to forward the form submission to a page (after the webform is validated) that indicates the task is processing. But surely there have to be some other solutions. And I am curious about what other solutions there are out there for this situation.
Thanks
I am just curious can be done to prevent a client from jamming away on a submit button on a webform?
I have been googling away for a few alternatives but most articles and suggestions I have found involve javascript. Such as http://dotnetjunkies.com/WebLog/mjordan/archive/2004/02/17/7393.aspx. Although this is a terrific solution, it doesn't prevent anyone from being a shyster and disabling javascript and abusing a webform. This can especially be a pain when the form submission involves inserting into a DB. The result being multiple rows inserted.
So there has be some sort of server side solution where if javascript is disabled the multiple form submissions can be ignored or prevented.
My current idea is to forward the form submission to a page (after the webform is validated) that indicates the task is processing. But surely there have to be some other solutions. And I am curious about what other solutions there are out there for this situation.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help guys.
I tried the http://metabuilders.com/Tools/OneClick.aspx webcontrol. And it did (usually) prevent multiple form submissions. Although I would get a strange behaviour where if the button was pressed more than once. It would perform the task I wanted performed once but refused to forward to a page after the process was complete. It would just sit on the page the form was submitted from. Submit could then be pressed again and viola 2 database inserts. In fact when I stepped through the code the Server.Transfer("Foo.aspx"
Gregory, when I added the GUID validation to the page it fixed the problem above. Now if the client hits submit more than once the task I need inserts to the database only once the GUID changes after the second button click and then the client is forwarded to a page saying their request has already been processed blah blah blah you hit submit more than once. Also the GUID validation prevents them from hitting back and re-submitting the form.
Thanks again, I am suprised there isn't a better system in place to handle the "javascript disabled" people in this scenario. What a pain it would be if someone wanted to be malicious and fill up a database with bunk data.
I tried the http://metabuilders.com/Tools/OneClick.aspx webcontrol. And it did (usually) prevent multiple form submissions. Although I would get a strange behaviour where if the button was pressed more than once. It would perform the task I wanted performed once but refused to forward to a page after the process was complete. It would just sit on the page the form was submitted from. Submit could then be pressed again and viola 2 database inserts. In fact when I stepped through the code the Server.Transfer("Foo.aspx"
Gregory, when I added the GUID validation to the page it fixed the problem above. Now if the client hits submit more than once the task I need inserts to the database only once the GUID changes after the second button click and then the client is forwarded to a page saying their request has already been processed blah blah blah you hit submit more than once. Also the GUID validation prevents them from hitting back and re-submitting the form.
Thanks again, I am suprised there isn't a better system in place to handle the "javascript disabled" people in this scenario. What a pain it would be if someone wanted to be malicious and fill up a database with bunk data.
neither of them handle the back button though (which atleast in my development has been a major issue due to peoples dumpy internet connections etc i.e. they get a this page cannot be displayed error)