This content has been marked as final. Show 3 replies
Some frameworks employ a generated token which is embedded in a hidden input field. This token is then submitted and server side a check can be made of that token was already "processed"; if so don't process it again. How you would do that is really up to you and depends on your capabilities and limitations; you could hold on the token information in the session or in a cookie for example.
For that I have implemented csrf Tokens. I am hoping for something on the client side only other than tokens.
client side = js.