Message 205204 - Python tracker

➜

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	brett.cannon, martin.panter, mcjeff, nadeem.vawda, orsenthil, python-dev, vstinner
Date	2013-12-04.07:43:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I think the fix for this bug only works if it gets the server to respond with a “Connection: close” header itself. I opened Issue 19524 because I was seeing keep-alive responses using chunked encoding that still trigger a socket leak.

I think the fix for this bug only works if it gets the server to respond with a “Connection: close” header itself. I opened Issue 19524 because I was seeing keep-alive responses using chunked encoding that still trigger a socket leak.

History
Date	User	Action	Args
2013-12-04 07:43:46	martin.panter	set	recipients: + martin.panter, brett.cannon, orsenthil, vstinner, nadeem.vawda, mcjeff, python-dev
2013-12-04 07:43:46	martin.panter	set	messageid: <[email protected]>
2013-12-04 07:43:46	martin.panter	link	issue11563 messages
2013-12-04 07:43:46	martin.panter	create