Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Should the AntiForgeryToken be applied to every post action in an ASP.NET MVC application? Off the top of my head I can’t think of any reason why you would not want to include this on every post action, but it seems that nobody ever actually recommends using it on all of your actions.
I’d love to hear your thoughts.
I always use it on POST/DELETE/PUT actions. I want to be as sure as I can that the request is coming from a page that my server sent to the browser when I’m changing data as a result.