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

cors-preflight needs to handle CORS non-wildcard request-header names #11

Open
tyoshino opened this issue Jul 29, 2016 · 3 comments
Open

Comments

@tyoshino
Copy link

tyoshino commented Jul 29, 2016

/cc @annevk

Like Access-Control-Allow-Headers, the headers item should have power to list Authorization header in addition to "*". CORSOptionList is currently specified to be "*" or a list, and therefore it cannot. The algorithm at 3.4.4. doesn't consider "*" in a list, and as a result it's giving more power to "*" than one in the Fetch Standard.

We can also choose to intentionally relax the requirement to list Authorization explicitly for Origin-Wide Policy, but needs to be discussed.

@tyoshino tyoshino mentioned this issue Jul 29, 2016
Closed
@annevk
Copy link

annevk commented Jul 29, 2016

Ah yeah, we should probably just match it indeed. And then if folks disagree they should argue to change CORS instead. I don't think we want to handle the security discussion on two fronts, so to speak.

@tyoshino
Copy link
Author

OK. Sounds good

@annevk
Copy link

annevk commented Feb 14, 2020

FWIW, I think this would be of potential interest to Mozilla, though I've also heard a suggestion of adding a extension bit to TLS to negotiate removal of these preflights, which would be even better performance-wise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants