-
Notifications
You must be signed in to change notification settings - Fork 2.1k
IgnoreAntiforgeryTokenAttribute possibly broken on 1.1.0 #5552
Comments
There's no intended change here. We need to take a look at this /cc @Eilon |
@ryanbrandenburg can you investigate, and also see if perhaps it's patch-worthy? (Is there a workaround?) |
FWIW, this bug also impacts Orchard 2's OpenID module, which worked fine with the 1.0.0 bits. |
The bug here is that this PR 01b237d should have also update the order value of If you need a workaround for this, I'd recommend setting |
Here's a convention that will fix it.
|
Done? |
Re-opening so we can take this for the 1.1.1 branch. |
@Eilon I assume this is an oversight but this is patch-approved not just patch-proposed right? I can go ahead with merging this commit into rel/1.1.2? |
Not yet approved, but soon! |
This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done. |
Also please remember that this is 1.1.2, so use the right branch! 😄 |
A little confuses, did this bug fixed? In asp.net core 1.1.1 or asp.net core mvc 1.1.2? |
@viewtance it's in ASP.NET Core MVC 1.1.2, which was released about a week ago: https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc/1.1.2 |
I have the following test application with a global filter for anti-forgery token validation and then a validation bypass on a specific action method:
Startup
Controller
Index view
Using the 1.0.1 MVC package I can access
/Test
, submit and get the successful response. However, if I use the 1.1.0 package I get a400 Bad Request
when submitting the formAm i missing something or did this behavior actually change?
The text was updated successfully, but these errors were encountered: