Message108147
| Author |
vstinner |
| Recipients |
vstinner |
| Date |
2010年06月18日.22:54:07 |
| SpamBayes Score |
0.020120028 |
| Marked as misclassified |
No |
| Message-id |
<1276901663.12.0.0713018653371.issue9032@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
See also r70643 (from issue #5542): "Remove special logic that closes HTTPConnection socket on EPIPE.
If the socket is closed, the client has no chance to read the response
from the server. EPIPE means that it isn't possible to write more
data from the socket, but not that it is impossible to read."
This commit didn't updated the following comment. I think that it should be fixed (maybe removed?) because the socket is no more closed on broken pipe error.
# send the data to the server. if we get a broken pipe, then close
# the socket. we want to reconnect when somebody tries to send again. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月18日 22:54:23 | vstinner | set | recipients:
+ vstinner |
| 2010年06月18日 22:54:23 | vstinner | set | messageid: <1276901663.12.0.0713018653371.issue9032@psf.upfronthosting.co.za> |
| 2010年06月18日 22:54:08 | vstinner | link | issue9032 messages |
| 2010年06月18日 22:54:07 | vstinner | create |
|