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 demian.brecht
Recipients Yuri.Bochkarev, agriffis, alanjds, amak, cananian, demian.brecht, icordasc, jcea, jhylton, martin.panter, mhammond, orsenthil, r.david.murray, rbcollins
Date 2015-01-20.18:10:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421777421.44.0.336241050337.issue3566@psf.upfronthosting.co.za>
In-reply-to
Content
Now I think I'd like to take my foot out of my mouth.

Previous quick experiments that I had done were at the socket level, circumventing some of the logic in the HTTPResponse, mainly the calls to readline() rather than simple socket.recv(<N>).

I've confirmed that the /only/ way that the HTTPConnection object can possibly get a 0-length read is, in fact, if the remote host has closed the connection.

In light of that, I have no objection at all to the suggested addition of ConnectionClosed exception and my apologies for the added confusion and dragging this issue on much longer than it should have been.

I've also attached my proof of concept code for posterity.
History
Date User Action Args
2015-01-20 18:10:21demian.brechtsetrecipients: + demian.brecht, jhylton, mhammond, jcea, orsenthil, amak, rbcollins, cananian, r.david.murray, alanjds, agriffis, martin.panter, icordasc, Yuri.Bochkarev
2015-01-20 18:10:21demian.brechtsetmessageid: <1421777421.44.0.336241050337.issue3566@psf.upfronthosting.co.za>
2015-01-20 18:10:21demian.brechtlinkissue3566 messages
2015-01-20 18:10:21demian.brechtcreate