Skip to content
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

FF115 Access-Control-Allow-Headers - wildcard not include Authorization header #20092

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

hamishwillee
Copy link
Collaborator

The spec states that if Access-Control-Allow-Headers specifies a wildcard, that does not automatically include the Authorization header. Browsers were wildcarding the Authorization header but are not preparing to deprecate that behaviour.

FF115 does so behind a preference in https://bugzilla.mozilla.org/show_bug.cgi?id=1687364. Chrome was planning to to this in M116 but is waiting on others to catch up: see https://chromestatus.com/feature/5742041264816128 and https://groups.google.com/a/chromium.org/g/blink-dev/c/yXxYCo3ytQU/m/Z6woo8enAgAJ

This adds the FF information.

Note, I have not been able to test this because the relevant WPT live test appears to fail this for other reasons: https://wpt.live/fetch/api/cors/cors-preflight-star.any.html

Related docs work can be tracked in mdn/content#27230

FYI @queengooborg

@github-actions github-actions bot added the data:http 🚠 Compat data for HTTP features. https://developer.mozilla.org/docs/Web/HTTP label Jun 12, 2023
@Elchi3 Elchi3 merged commit aff63e4 into mdn:main Jun 12, 2023
3 checks passed
@hamishwillee hamishwillee deleted the ff115_access_control_auth branch June 13, 2023 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:http 🚠 Compat data for HTTP features. https://developer.mozilla.org/docs/Web/HTTP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants