CORS exception regex#173
Merged
das-Abroxas merged 5 commits intomainfrom May 13, 2024
Merged
Conversation
St4NNi
approved these changes
May 13, 2024
Member
St4NNi
left a comment
St4NNi
left a comment
There was a problem hiding this comment.
Maybe not the best solution, but works for now. LGTM
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a config parameter that can be used to set CORS exceptions for certain origins via regex.
Requests with an
Originheader whose value matches the regex always receive the following CORS response headers in the response:Access-Control-Allow-Origin: *Access-Control-Allow-Methods: *Access-Control-Allow-Headers: *This allows the operators of a DataProxy to release its resources for interactions with certain applications. If the parameter is not set, only the set bucket CORS rules are applied as before.