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.

Sign up for GitHub

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

Jump to bottom

CORS-safelisting particular client hints #1383

Open
eeeps opened this issue Jan 19, 2022 · 1 comment
Open

CORS-safelisting particular client hints #1383

eeeps opened this issue Jan 19, 2022 · 1 comment
Labels
topic: client hints topic: cors

Comments

@eeeps
Copy link

eeeps commented Jan 19, 2022

Now that there is not a generic safelist carve-out for all Sec--prefixed request headers, we will need to safelist individual client hints as they become part of the platform.

I believe the best list of current hints is in Client Hints Infrastructure. These are at various stages of consensus/maturity; none of them are currently implemented anywhere besides Chrome. Chrome does not preflight when adding any of them.
@annevk
Copy link
Member

annevk commented Jan 24, 2022

See WICG/client-hints-infrastructure#100.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: client hints topic: cors
Milestone
No milestone
Development

No branches or pull requests
2 participants
@annevk @eeeps