Change to regex allowed settings for CORS in API server #1420
+7
−21
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
When supports_credentials is True, the server cannot return `Access-Control-Allow-Origin: *` . It must echo back the specific requester's origin. `flask-cors` handles this automatically if you provide a list or a regex, but it won't work with a literal `*` string in some browser implementations.
adamoutler
force-pushed
the
patch-9
branch
2 times, most recently
from
f0eab60 to
09fc1f3
Compare
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When supports_credentials is True, the server cannot return
Access-Control-Allow-Origin: *. It must echo back the specific requester's origin.flask-corshandles this automatically if you provide a list or a regex, but it won't work with a literal*string in some browser implementations.