Skip to content

Make Content-Type CORS request check stronger #29701

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

If a Content-Type request header contains multiple comma separated
value, this change makes sure to check that all of them are safelisted
and otherwise triggers a CORS preflight.

Bug: 1155640
Change-Id: I75f5d1e4a51b876caea102de5c26afb5bfa090d1
Reviewed-on: https://chromium-review.googlesource.com/3031304
WPT-Export-Revision: bd4190b49ef22b1f1195a76d440f323490b68704

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

If a Content-Type request header contains multiple comma separated
value, this change makes sure to check that all of them are safelisted
and otherwise triggers a CORS preflight.

Bug: 1155640
Change-Id: I75f5d1e4a51b876caea102de5c26afb5bfa090d1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants