➜

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 Jason Morawski
Recipients Jason Morawski, asvetlov, kristjan.jonsson, mikeputnam, neologix, pitrou, python-dev, vdjeric
Date 2015-10-13.18:56:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444762606.14.0.335134394463.issue14574@psf.upfronthosting.co.za>
In-reply-to
Content 
Found another issue with this in 2.7

If the socket.error gets raised from the call to self.wfile.flush(), then when self.wfile.close() is called, self.wfile.flush() is called a second time if self.wfile._wbuf is not empty. This will raise the socket.error again. Attaching a patch that explicitly clears the buffer when the socket.error occurs.
History
Date User Action Args
2015-10-13 18:56:46Jason Morawskisetrecipients: + Jason Morawski, pitrou, kristjan.jonsson, asvetlov, mikeputnam, neologix, python-dev, vdjeric
2015-10-13 18:56:46Jason Morawskisetmessageid: <1444762606.14.0.335134394463.issue14574@psf.upfronthosting.co.za>
2015-10-13 18:56:46Jason Morawskilinkissue14574 messages
2015-10-13 18:56:46Jason Morawskicreate