Home/ Questions/Q 6811809
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T20:22:20+00:00

I know this is a basic question, but I am curious as to what

  • 0

I know this is a basic question, but I am curious as to what the different options are, and what the best practice would be.

If I have a form that is responsible for saving reservations into a system, how can I prevent the form from being posted twice if the user hits the button twice really quickly?

I know there are a few ways in which I can accomplish this, but I am not quite sure which is the standard way of preventing this. Partially because I am new to web forms, and am used to dealing with MVC.

Thanks ahead of time.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve used two approaches to this problem:

    1. Use a token based approach. Each page has a hidden input with the current random token. This token is also stored in the user’s session. Once the postback occurrs, I compare tokens and, if they are valid, generate a new session token and continue processing. When the second postback occurs, the token no longer matches and prevents processing.

    2. Use javascript to disable the submit button. If you take this approach, and need the button event handler to fire, you’ll need to create a hidden input with the name attribute of the button before submitting. The hidden input is required because disabled inputs do not end up in the post data.

    • 0