I am using an MVC4 anti-forgery token created with @Html.AntiForgeryToken(). I have a problem as follows:
- The application opens and a login form is generated for the first time with an antiforgery token for user name of "".
- The login form is cached in the browser
- The user goes to another page
- User clicks the back button and goes back to the login page.
- Login page is displayed from cache and still has a token for user name of "".
Is there a way in MVC that I can make it so when a user clicks the back button and goes to the login page he is not presented with a cached version.