-
Notifications
You must be signed in to change notification settings - Fork 4.9k
fix(plugin/cors): treat empty Origin header same as missing header #14368
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
Conversation
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.
Overall LGTM. Not a blocker but please take a look
Hi @StarlightIbuki 👋, a friendly ping to let me know if there's anything I can clarify or adjust to move this forward. |
changelog/unreleased/kong/fix-cors-allow-empty-string-origin.yml
Outdated
Show resolved
Hide resolved
@dingjiayi Hi. Please address the new comments. Our policy requires 2 approvals from maintainers to merge a PR. |
Thanks for your contribution! After all CI goes green this PR will be merged |
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.
LGTM
Summary
This change ensures that an empty Origin header (
Origin: ""
) is treatedthe same way as a missing Origin header, fixing inconsistent behavior
between these two cases.
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
Fix #14352