Sijin Joseph <sijinjos...@gmail.com> added the comment: Looking at the code in httplib it seems that response.will_close is set under the following circumstances,
1. HTTP version is 0.9 2. HTTP response header connection is set to close 3. Non-chunked content with a length of zero This suggests that the underlying socket closure is valid under the conditions and that a subsequent response.read() should not be returning any content. If you think this is still an issue, I'd suggest that you create a small example client/server script that Client: 1. Opens a HTTP connection 2. Continues to read data from it and dumps it to the console. Server: 1. Setup a script that does not close incoming HTTP connection requests and continues to keep sending data back to the client. ---------- nosy: +sijinjoseph _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7806> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
