Bryan Bishop added the comment:
I'll go ahead and close this. The putrequest/putheader/endheaders suggestion is
probably sufficient. Although I do wonder if a docs update is warranted,
explaining the default behavior..
--
resolution: -> wont fix
stage: -> resolved
status: p
Bryan Bishop added the comment:
On Tue, Jan 1, 2013 at 5:41 AM, Antoine Pitrou wrote:
Another possibility would be to allow passing None in values of the `headers`
dict, in which case the given header wouldn't be send at all.
I agree that your solution is more scaling-friendly than the patch
New submission from Bryan Bishop:
Sometimes I am using httplib/http.client and the server is not exactly
conforming to HTTP specs. I need to be able to specify the exact headers that
are sent to the server. By default, httplib/http.client injects headers like
Host and Accept-Encoding.
Issue