Senthil Kumaran orsent...@gmail.com added the comment:
Not an issue anymore as socket timeout at client is supposed to happen with the
connection is hung due to unresponsive host.
The original bug was raised py2.3. Closing it as out of date.
--
nosy: +orsenthil
resolution: - out of
Charles-Francois Natali neolo...@free.fr added the comment:
Skimming through the code, the only place where we can reasonably block is
inside HTTPConnection._send_output(), when the data is actually sent to the
socket.
What probably happens is the following:
- connect() call succeeded, we have
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Is this still a problem with later versions of Python?
--
nosy: +BreamoreBoy
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
Changes by Giampaolo Rodola' g.rod...@gmail.com:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1531775
___
___
Daniel Diniz aja...@gmail.com added the comment:
This needs a test case reproducing the 'unexpected close'.
--
nosy: +ajaksu2
stage: - test needed
type: - behavior
versions: +Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
