Real life situation: placing bets on a betting website. Users would double click and get two bets placed. Not good! Javascript checks were not sufficient to prevent this. Solution: Create UUID/GUID hidden input in form using server-side scripting language that renders the form. On form submission immediately add this to a database table called UniqueSubmissions … Read more
If you’re using solely ajax requests, you could use jsf.ajax.addOnEvent handler of the JSF JavaScript API for this. The below example will apply on all buttons of type=”submit”. function handleDisableButton(data) { if (data.source.type != “submit”) { return; } switch (data.status) { case “begin”: data.source.disabled = true; break; case “complete”: data.source.disabled = false; break; } } … Read more
The standard way is to do it in 3 steps. the form page submits fields to processing page processing page processes data and redirects to result page result page just displays results, reloading it won’t do any harm.
I am looking for generic mechanism to avoid form re-submission when the page is refreshed For that there are at least 2 solutions which can not be combined: Perform a redirect after synchronous post. This way the refresh would only re-execute the redirected GET request instead of the initial request. Disadvantage: you can’t make use … Read more
“ASP.NET is preventing the click event being called more than once. Is this true?” No, actually what is happening to you is that your events are blocked by the lock of the session. (What session is on asp.net, is a module on asp.net that can keeps data for each user that visit the site) So … Read more
Update in 2018: I just got some points for this old answer, and just wanted to add that the best solution would be to make the operation idempotent so that duplicate submissions are harmless. Eg, if the form creates an order, put a unique ID in the form. The first time the server sees an … Read more