Fix #216: HttpMessage._add_default_headers does not overwrite existing headers#219
Merged
Conversation
Member
|
+1 for useragent i'm not sure about server and date, here is reason: |
Member
|
+1 for server and date |
Member
|
+1 |
asvetlov
added a commit
that referenced
this pull request
Jan 2, 2015
Fix #216: HttpMessage._add_default_headers does not overwrite existing headers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have had drop SERVER and DATE from hop-by-hop headers also.
According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html 13.5.1 End-to-end and Hop-by-hop Headers those headers are not in hop-by-hop list.