The provided anti-forgery token was meant for user "", but the current user is

Posted: April 05, 2013 at 12:01 AM Quote #93377
Hi, I have been getting the occasional error message logged with nopCommerce version 2.80 The provided anti-forgery token was meant for user "", but the current user is. It seem to happen when a previous 'guest' comes back later and then registers.
Any help to fix this would be greatly appriciated, as it results in a potential new customer then abandoning my site
This post/answer is useful
1
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Posted: July 02, 2013 at 12:12 PM Quote #100253
I'm having this same problem with nop 3.0
This post/answer is useful
0
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Posted: July 07, 2014 at 1:26 PM Quote #126091
Im using nop 3.3.

In my case, our test team got this error following these steps:

1- register
2- on confirmation screen, click browser Back button
3- submit the registration form again
4- the "email already exists" information is displayed
5- click submit button again.
6- untreated error appears "The provided anti-forgery token was meant for user..."

Is there a fix for this bug? We dont want to modify the core, because of future updates.
This post/answer is useful
0
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Posted: September 19, 2014 at 1:50 AM Quote #131191
http://www.nedoweb.com/Blog/tabid/60/EntryId/23/The-provided-anti-forgery-token-was-meant-for-user-but-the-current-user-is-myUsername.aspx
This post/answer is useful
0
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
nopCommerce on facebook