-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
http.CanonicalHeaderKey isn't correct #823
Labels
Comments
CanonicalHeaderKey is definitely correct. The server could emit everything lower case if it wanted to (and maybe it should, just to make the point). Clients or servers that insist on a particular case are in violation of the RFC. http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2 Field names are case-insensitive. Status changed to WorkingAsIntended. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by lukenine45:
The text was updated successfully, but these errors were encountered: