This repository has been archived by the owner on Nov 1, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 58
AspNetCoreModule throws 500 error for requests that specify relative quality in the Accept header #262
Comments
What makes you think this is an AspNetCoreModule issue? Does it reproduce if you run Kestrel independently? |
To be honest, I'm not sure - it could be a Kestrel issue (I will run some tests now). I assumed it was the module issue because I don't see the error with RC1 apps running under the HttpPlatformHandler module. Also, this error appears to occur before any application or Kestrel code is invoked. |
Well, it looks like you're right. Running directly under Kestrel I can see that the error is in there:
Seems like you should get a better error than 500.0 though, right? |
Sorry, looks like I should be filing an issue in the Mvc repo. Thanks for pointing me in the right direction. |
Looks like a duplicate of aspnet/Mvc#5150 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
IIS & IIS Express return a 500.0 response for a request that specifies a q=# in the Accept header
Functional impact
Causes all requests to fail mysteriously with a 500 response generated by the AspNetCoreModule.
Minimal repro steps
Finally found this cause of some mysterious 500 errors we were seeing in our APIs. If you specify an Accept header to any API request, such as:
text/html, *; q=.2, */*; q=.2
The AspNetCoreModule will fail with a 500 error.
To reproduce this in IIS or IIS express:
Important: This bug does not appear in .NET Core applications running under RC1 (which I believe uses a different IIS module).
Expected result
The request should succeed.
Actual result
The request returns a non-descript 500.0 error: IIS failed request trace logging reveals this:
The text was updated successfully, but these errors were encountered: