➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients jcea, martin.panter, orsenthil, r.david.murray, s7v7nislands@gmail.com, sanxiago, shubhojeet.ghosh
Date 2015-05-23.02:04:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432346667.74.0.649512366226.issue12849@psf.upfronthosting.co.za>
In-reply-to
Content 
So far the only reasons that have been given to override this header (mine and the one in Issue 15943) seem to be to work around buggy servers. It is already documented that HTTP 1.1 and “Connection: close” are used, so if this issue is only about working around buggy servers, the best thing might be to close this as being “not a Python bug”. The user can always still use the low-level HTTP client, or make a custom urllib.request handler class (which is what I did).

Shubhojeet: What was the reason you wanted to set a keep-alive header?

If this is about proper keep-alive (a.k.a persistent) connection support in urllib.request, perhaps have a look at Issue 9740.
History
Date User Action Args
2015-05-23 02:04:27martin.pantersetrecipients: + martin.panter, jcea, orsenthil, r.david.murray, shubhojeet.ghosh, sanxiago, s7v7nislands@gmail.com
2015-05-23 02:04:27martin.pantersetmessageid: <1432346667.74.0.649512366226.issue12849@psf.upfronthosting.co.za>
2015-05-23 02:04:27martin.panterlinkissue12849 messages
2015-05-23 02:04:26martin.pantercreate