This is actually not an update to the page you want to block, its POST page.
As already mentioned, this is not possible on the client side, because the update will reproduce what the browser did in the last action.
But you can lure it to the server, because the server can store some information to manage the request.
The easiest way is to put the RequestID view in a hidden field in Page Load , save it somewhere, like in Session . And control its value in the next POST to execute the request, then redefine it to avoid re- POST with the same RequestID.
Maybe the best way :)
Your βproblemβ is similar to user double-click behavior: ASP.Net double-click problem
source share