Add note for CORS: Wildcard Headers and Methods feature support #5116
Conversation
This file contains 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
kiding
reviewed
Oct 6, 2019
| "66":"y #4", | ||
| "67":"y #4", | ||
| "68":"y #4", | ||
| "61":"y #4 #5", |
There was a problem hiding this comment.
This is a bit weird to me. Looks like 4 and 5 suddenly appeared at version 61.
The same goes to the other changes; 5 suddenly appeared at version X, then disappeared at version Y.
|
fwiw, this is also in caniuse via the MDN data, see https://caniuse.com/#search=wildcard |
|
@Elchi3 That is interesting. It's a bit unfortunate though because one wouldn't know to look for it currently when looking for CORS support in browsers. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Many browsers do not support wildcard "Access-Control-Allow-Headers" and "Access-Control-Allow-Methods".