The anti-forgery token could not be decrypted
(Automatically adding template at the end of the page.)
(Replacing message template with parser tag)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<message>Write the content here to display this box</message>
  The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the &amp;lt;machineKey&amp;gt; configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster.
  The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the &amp;lt;machineKey&amp;gt; configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster.
This page produced by us contains an ID (antiforgerytoken) - it is new each time.  
This page produced by us contains an ID (antiforgerytoken) - it is new each time.  

Latest revision as of 07:58, 17 June 2024

The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the &lt;machineKey&gt; configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster.

This page produced by us contains an ID (antiforgerytoken) - it is new each time.

It is generated from a key value on the server (machineKey).

If you have a webfarm (more than one frontend), this key value on the server should be the same for all servers.

When ASP.NET gets a postback from a page with an anti-forgery token, it tries to verify it.

The goal is to avoid someone taking an old page and re-posting it multiple times.

If you wait for a long time from page gen to postback, the token may expire.

This page was edited 104 days ago on 06/17/2024. What links here