Databases
StackOverflow2013
Postsdbo
PORequestVerificationToken does not match
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORequestVerificationToken does not match
    primarykey
    data
    text
    <p>I have a problem with the anti CRSF MVC mechanism. The cookie and the form input returned does not match. I'm getting an error every single time, only in one specific page. In the rest of the application it works well.</p> <p>The server is returning <code>HTTP 500 Internal Server Error</code> and I can see on the log this exception:</p> <blockquote> <p>[System.Web.Mvc.HttpAntiForgeryException]: {"A required anti-forgery token was not supplied or was invalid."}</p> </blockquote> <p>This is the hidden input that the server is generating is:</p> <pre><code>&lt;input name="__RequestVerificationToken" type="hidden" value="QK8P7rjyZE6Vm5seY7Fr704YCOoFGdTIMzl1W7R0ZFpXSMjGKLG2T05DfFSYTxvtQCEx7DDT69DGsDB2+ZXFHY8oAjiKz0gw8BhDFywgmfIpoXnGpj7fONNzIIfvbrDrE9WJsMu6Io/0bDLM5WfKs0zktiNjyOWpfYrmnfINYmjW8NLOZFoz74xTcgTptAld"&gt; </code></pre> <p>And this is the Cookie returned:</p> <pre><code>Set-Cookie:__RequestVerificationToken_L2VGbG93=skmTAVI8HCbfxDS+xhioIMIISL3UOBI7qJM1JbHjTtAqKl4W70pDUcTKMm0p3R3mrHDziE8vXw0C0OO4HArzWO1/e6py+v/cFdbe9maFgjl4jMiZ9Wc4YIhC6+IUXkk6yqJDJ8dCIr8qtGaYcD9IX+m7/SlVhu521KQSWJYRcaY=; path=/; HttpOnly </code></pre> <p>When I examine what the server is sending, the cookie is exactly the same, but the payload has different encoding I think:</p> <pre><code>__RequestVerificationToken:QK8P7rjyZE6Vm5seY7Fr704YCOoFGdTIMzl1W7R0ZFpXSMjGKLG2T05DfFSYTxvtQCEx7DDT69DGsDB2%2BZXFHY8oAjiKz0gw8BhDFywgmfIpoXnGpj7fONNzIIfvbrDrE9WJsMu6Io%2F0bDLM5WfKs0zktiNjyOWpfYrmnfINYmjW8NLOZFoz74xTcgTptAld </code></pre> <p>The differences are in two characters that appear encoded:</p> <pre><code> / -&gt; %2F + -&gt; %2B </code></pre> <p>Those are the only differences I can find between the hidden input field, and the post payload. </p> <p>What could be the problem that is causing that <code>ValidateAntiForgeryToken</code> fails in verify the token?</p> <p>Regards.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCharles
    1. USvtortola
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORequestVerificationToken does not match
      1. USstevenrcfox
      1. VTBountyStart
    2. VO
      singulars
      1. PORequestVerificationToken does not match
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORequestVerificationToken does not match
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe encoding will not affect the processing of the token and cookie. Please provide details about the page with the issue, and the action being used to transmit the request to your action. In addition (first really), inspect the failing request with Fiddler or a similar tool, and confirm that the token and cookie are both being transmitted.
      singulars
      1. PORequestVerificationToken does not match
      1. UScounsellorben
    2. COI can confirm that both the cookie and the input are being sent to the server.
      singulars
      1. PORequestVerificationToken does not match
      1. USvtortola
    3. COCan you please provide details about the view and the action where you are having the problem. The most likely issue would be if you are using a salt, and the salts don't match, but there is no way to diagnose this if you won't provide details.
      singulars
      1. PORequestVerificationToken does not match
      1. UScounsellorben
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload