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

Clarify Access-Control-Request-Headers (#33313) #33318

Merged
merged 1 commit into from
May 1, 2024
Merged

Conversation

jub0bs
Copy link
Contributor

@jub0bs jub0bs commented Apr 29, 2024

Description

Be more precise about the format of the Access-Control-Request-Headers header.

Motivation

Imprecision can give practitioners false expectations.

Related issues and pull requests

Fixes #33313

@jub0bs jub0bs requested review from a team as code owners April 29, 2024 18:03
@jub0bs jub0bs requested review from teoli2003 and removed request for a team April 29, 2024 18:03
@github-actions github-actions bot added Content:HTTP HTTP docs Content:Glossary Glossary entries size/s [PR only] 6-50 LoC changed labels Apr 29, 2024
@sideshowbarker sideshowbarker merged commit 38fb31b into mdn:main May 1, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Glossary Glossary entries Content:HTTP HTTP docs size/s [PR only] 6-50 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Imprecise Access-Control-Request-Headers examples give practitioners false expectations
2 participants