EnableHttpLogging causes anti forgery token verification error during partial log in.

[kylesonaty]

I have a partial log in where we migrate users accounts.

 [HttpPost]
 [ValidateAntiForgeryToken]
 public async Task<ActionResult> Index(UsernameToEmailInputModel model)

and the @Html.AntiForgeryToken() is in the view and inside the form.

If the logging options are setup in the IdentityServerOptions has HTTP logging enabled

LoggingOptions = new LoggingOptions { EnableHttpLogging = true }

I will receive a generic error stating that The required anti-forgery form field “__RequestVerificationToken” is not present Error in user Registration

If I remove the anti forgery token from the view and the controller I get
“This method or property is not supported after HttpRequest.GetBufferlessInputStream has been invoked.”

[brockallen]

Mind checking something for me? Remove the [ValidateAntiForgeryToken] and see if you get any of your inputs in your MVC action method. I suspect you will not.

[brockallen]

So BTW, I have feeling this is an issue between WebAPI and ASP.NET -- WebAPI is consuming the entire request buffer (for the logging) and then outside of Web API (meaning ASP.NET) something's now broken/gone in the buffer.

[kylesonaty]

If I remove the [ValidateAntiForgeryToken] I get this error
“This method or property is not supported after HttpRequest.GetBufferlessInputStream has been invoked.” and it never makes it to the method.

[brockallen]

Right -- so we need to discuss, but I don't think there's much we can do. This is the two frameworks fighting each other.

[leastprivilege]

not much we can do here. Unless someone has an idea. closing for now.