-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
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
feat: add allow_origins_by_regex to cors plugin #3839
Merged
spacewander
merged 11 commits into
apache:master
from
batman-ezio:feature/allow_origins_by_regex
Mar 22, 2021
Merged
Changes from 10 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
c648694
feat: add allow_origins_by_regex to cors plugin
ezioruan 7798a28
feat: add allow_origins_by_regex to cors plugin
ezioruan 14cd781
feat: add allow_origins_by_regex to cors plugin
ezioruan e60a7c7
feat: add allow_origins_by_regex to cors plugin
ezioruan eb54f7c
feat: add allow_origins_by_regex to cors plugin
ezioruan 58b45ed
feat: add allow_origins_by_regex to cors plugin
ezioruan dc87949
feat: add allow_origins_by_regex to cors plugin
ezioruan 02978ea
feat: add allow_origins_by_regex to cors plugin
ezioruan 57a8e20
feat: add allow_origins_by_regex to cors plugin
ezioruan 7b408fe
feat: add allow_origins_by_regex to cors plugin
ezioruan 95cc60c
feat: add allow_origins_by_regex to cors plugin
ezioruan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't understand why we need
or conf.allow_origins_by_regex ~= nil
.If
allow_origins_by_regex
is given but not matched, it can't go into this function.If
allow_origins_by_regex
is given but matched, thecors_allow_origins
can't be*
as*
is just a mark used inallow_origins
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if allow_origins_by_regex is matched, the cors_allow_origins will be the matched domain. not
*
for example. it we use
[".*.test.com"]
and the request is from a.test.comthen the cors_allow_origins will set to
a.test.com
. not*
conf.allow_origins_by_regex ~= nil
means we use regex to match many domains.the Vary must set as
Origin
f a request may contain a Access-Control-Allow-Origin with different values, then the CDN should always respond with Vary: Origin,
check
https://stackoverflow.com/questions/25329405/why-isnt-vary-origin-response-set-on-a-cors-miss
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
So
ctx.cors_allow_origins ~= "*"
will be true.Therefore there is no need to add an additional condition.