-
Notifications
You must be signed in to change notification settings - Fork 330
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
define how header name case sensitivity works #8
Comments
Most direct solution for implementing this appears to be lower-casing the header name in all cases. |
Paging @horo-t as a heads up. I'm planning on specifying lowercased header names later today. |
After @annevk will change the spec, I will change the codes in Chromium. |
yutakahirano
added a commit
that referenced
this issue
Jun 23, 2020
# This is the 1st commit message: # This is a combination of 23 commits. # This is the 1st commit message: Integrate CORP and COEP This is part of the introduction of COEP (whatwg/html#5454). The CORP check now takes COEP into account. Also, responses coming from service workers are checked. # This is the commit message #2: Update fetch.bs Co-authored-by: Domenic Denicola <d@domenic.me> # This is the commit message #3: Update fetch.bs Co-authored-by: Domenic Denicola <d@domenic.me> # This is the commit message #4: fix # This is the commit message #5: fix # This is the commit message #6: fix # This is the commit message #7: fix # This is the commit message #8: fix # This is the commit message #9: fix # This is the commit message #10: fix # This is the commit message #11: fix # This is the commit message #12: fix # This is the commit message #13: fix # This is the commit message #14: fix # This is the commit message #15: fix # This is the commit message #16: fix # This is the commit message #17: fix # This is the commit message #18: Update fetch.bs Co-authored-by: Anne van Kesteren <annevk@annevk.nl> # This is the commit message #19: Update fetch.bs Co-authored-by: Anne van Kesteren <annevk@annevk.nl> # This is the commit message #20: fix # This is the commit message #21: fix # This is the commit message #22: fix # This is the commit message #23: fix # This is the commit message #2: fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you do the following:
headers.append("accept", "text/plain")
headers.append("Accept", "application/x-www-form-urlencoded")
I assume all of these should return an array of two items:
headers.getAll("accept");
headers.getAll("Accept");
headers.getAll("ACCEPT");
But if we have to serialize out, does it matter what form of the header case should be used?
I propose allowing the browser to select a single case for output serialization, iteration, etc. Preserving case seems relatively unimportant and would require memory/complexity.
The text was updated successfully, but these errors were encountered: