We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From @rynowak on Wednesday, June 14, 2017 1:31:11 PM
Right here, we ignore an OPTIONS request without the AccessControlRequestMethod header, and treat it as a non-preflight request.
OPTIONS
AccessControlRequestMethod
We should log specifically when this happens, it's important to know why in this case the request is being treated as non-preflight.
What will typically happen is that your CORS-ing in front of an API, and that API won't support OPTIONS, so you get a 404.
Copied from original issue: aspnet/CORS#113
The text was updated successfully, but these errors were encountered:
Log when a request is an OPTIONS request but not a preflight request
fb649d4
Fixes dotnet/aspnetcore#2375
1b7e95c
a4079ad
e6bdf12
ping timeout changes (#2375)
e3835b3
documentation updates
pranavkm
No branches or pull requests
From @rynowak on Wednesday, June 14, 2017 1:31:11 PM
Right here, we ignore an
OPTIONS
request without theAccessControlRequestMethod
header, and treat it as a non-preflight request.We should log specifically when this happens, it's important to know why in this case the request is being treated as non-preflight.
What will typically happen is that your CORS-ing in front of an API, and that API won't support
OPTIONS
, so you get a 404.Copied from original issue: aspnet/CORS#113
The text was updated successfully, but these errors were encountered: