set Accept headers #296
Open
set Accept headers #296
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to [w3 rules](http://www.w3.org/TR/cors/#cors-preflight-fetch) we have to set accept headers to `*/*` for every OPTIONS request
Thank you for taking the time to make a PR. In my read of the W3 spec, the accept header should be specified by the client. Did you run into an issue whc |
|
Thanks for reviewing the PR. I believe since it is a pre-flight request we need to intimate to the user data type accepted in the real request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to w3 rules we have to set accept headers to
*/*for every OPTIONS request