[issue15633] httplib.response is not closed after all data has been read

2013-02-02 Thread Nikolaus Rath
Nikolaus Rath added the comment: On 01/29/2013 11:23 PM, Antoine Pitrou wrote: > "length: 9369540" indicates you haven't read the whole advertised > Content-Length. Is it possible the server shuts down the TCP connection even > before the whole Content-Length has been sent? The remote server i

[issue15633] httplib.response is not closed after all data has been read

2013-02-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: I've committed the patch into 2.7 and then ported it to 3.x. Please reopen if the problem still occurs with the patch. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Pyt

[issue15633] httplib.response is not closed after all data has been read

2013-02-02 Thread Roundup Robot
Roundup Robot added the comment: New changeset 03c536afeb7e by Antoine Pitrou in branch '3.2': Issue #15633: httplib.HTTPResponse is now mark closed when the server sends less than the advertised Content-Length. http://hg.python.org/cpython/rev/03c536afeb7e New changeset 7d504068bc58 by Antoine

[issue15633] httplib.response is not closed after all data has been read

2013-02-02 Thread Roundup Robot
Roundup Robot added the comment: New changeset 8dcf94c2fef5 by Antoine Pitrou in branch '2.7': Issue #15633: httplib.HTTPResponse is now mark closed when the server sends less than the advertised Content-Length. http://hg.python.org/cpython/rev/8dcf94c2fef5 -- nosy: +python-dev ___

[issue15633] httplib.response is not closed after all data has been read

2013-01-30 Thread Antoine Pitrou
Antoine Pitrou added the comment: Here is a patch for 2.7. Ideally, we would raise IncompleteRead in this situation, but this would break existing programs. -- keywords: +patch stage: -> patch review versions: +Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file2

[issue15633] httplib.response is not closed after all data has been read

2013-01-29 Thread Antoine Pitrou
Antoine Pitrou added the comment: "length: 9369540" indicates you haven't read the whole advertised Content-Length. Is it possible the server shuts down the TCP connection even before the whole Content-Length has been sent? -- ___ Python tracker

[issue15633] httplib.response is not closed after all data has been read

2013-01-29 Thread Nikolaus Rath
Nikolaus Rath added the comment: Alright, it *finally* happened again. Attributes of the response object are: ._method: GET, .chunked: 0, .length: 9369540 .chunk_left: UNKNOWN, .status: 200 .reason "OK", .version: 11, .will_close: False -- ___

[issue15633] httplib.response is not closed after all data has been read

2012-10-22 Thread Piotr Dobrogost
Piotr Dobrogost added the comment: @Nikolaus Issue 16298 was raised today describing what could be the cause of what you observe. -- ___ Python tracker ___ _

[issue15633] httplib.response is not closed after all data has been read

2012-10-22 Thread Nikolaus Rath
Nikolaus Rath added the comment: This is just a heads-up that I'm still trying to debug this. So far, the problem doesn't seem to have shown up again (for reference, the original report for this is http://code.google.com/p/s3ql/issues/detail?id=358). -- ___

[issue15633] httplib.response is not closed after all data has been read

2012-10-22 Thread Piotr Dobrogost
Changes by Piotr Dobrogost : -- nosy: +piotr.dobrogost ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue15633] httplib.response is not closed after all data has been read

2012-08-14 Thread Nikolaus Rath
Nikolaus Rath added the comment: The call should be read(size), with size a number. I will make sure to check size, "fp", "length", "chunked" and "chunk_left" when it happens the next time. -- ___ Python tracker _

[issue15633] httplib.response is not closed after all data has been read

2012-08-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Do you call read() or read()? Please inspect at least the "fp", "length", "chunked" and "chunk_left" attributes. -- nosy: +pitrou ___ Python tracker _

[issue15633] httplib.response is not closed after all data has been read

2012-08-13 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue15633] httplib.response is not closed after all data has been read

2012-08-13 Thread Nikolaus Rath
Nikolaus Rath added the comment: The problem seems to occur regularly, just with large intervals in between. Is there any specific information that might help here? I am not quite sure what to save when the problem happens the next time. Can the response object be pickled? -- ___

[issue15633] httplib.response is not closed after all data has been read

2012-08-13 Thread R. David Murray
R. David Murray added the comment: Without a reproducible test case I doubt we are going to be able to solve this, but yes please provide what information you can for the record, in case someone else runs in to it in a more reproducible situation. -- nosy: +r.david.murray

[issue15633] httplib.response is not closed after all data has been read

2012-08-12 Thread Nikolaus Rath
New submission from Nikolaus Rath: Occasionally, the isclosed() method of HTTPResponse instances returns False, even though a preceding read() call returned '' (or something else that evalues to False). This is a problem, because then the corresponding HTTPConnection can still be used to send