Files
node-v0.x-archive/lib
isaacs c9dcf5718c http: Raise hangup error on destroyed socket write
Prior to v0.10, Node ignored ECONNRESET errors in many situations.
There *are* valid cases in which ECONNRESET should be ignored as a
normal part of the TCP dance, but in many others, it's a very relevant
signal that must be heeded with care.

Exacerbating this problem, if the OutgoingMessage does not have a
req.connection._handle, it assumes that it is in the process of
connecting, and thus buffers writes up in an array.

The problem happens when you reuse a socket between two requests, and it
is destroyed abruptly in between them.  The writes will be buffered,
because the socket has no handle, but it's not ever going to GET a
handle, because it's not connecting, it's destroyed.

The proper fix is to treat ECONNRESET correctly.  However, this is a
behavior/semantics change, and cannot land in a stable branch.

Fix #4775
2013-02-14 16:03:40 -08:00
..
2011-03-14 17:37:05 -07:00
2012-07-06 19:28:35 -07:00
2011-03-14 17:37:05 -07:00
2013-01-08 04:32:40 +01:00
2013-01-18 12:13:32 +01:00
2012-09-25 11:08:52 -07:00
2011-03-14 17:37:05 -07:00
2012-12-12 09:46:22 +01:00
2012-08-24 16:56:06 +02:00
2012-02-27 14:03:18 -08:00
2012-06-19 14:07:48 -07:00
2012-06-28 10:14:03 -07:00
2013-01-18 03:48:05 +04:00
2012-03-03 23:48:57 -08:00