isaacs
025f9133bb
http: Don't try to destroy nonexistent sockets
...
Fixes #3740
In the case of pipelined requests, you can have a situation where
the socket gets destroyed via one req/res object, but then trying
to destroy *another* req/res on the same socket will cause it to
call undefined.destroy(), since it was already removed from that
message.
Add a guard to OutgoingMessage.destroy and IncomingMessage.destroy
to prevent this error.
2013-04-22 10:38:14 -07:00
..
2012-12-14 10:52:28 -08:00
2013-04-17 00:08:28 +02:00
2013-04-17 00:08:28 +02:00
2013-04-17 00:08:28 +02:00
2013-04-22 10:38:14 -07:00
2013-04-22 10:38:14 -07:00
2013-04-17 00:08:28 +02:00
2011-03-14 17:37:05 -07:00
2013-01-17 10:42:44 -08:00
2013-03-05 14:27:15 -08:00
2013-04-11 16:12:48 -07:00
2013-04-05 12:05:58 -07:00
2013-04-09 02:09:51 +04:00
2013-04-19 16:25:11 -07:00
2013-04-12 11:30:11 -04:00
2013-04-11 13:53:18 +02:00
2013-04-20 22:58:16 +02:00
2013-03-12 13:15:03 -07:00
2011-03-14 17:37:05 -07:00
2013-04-12 11:30:11 -04:00
2013-04-18 00:54:57 +02:00
2013-03-06 14:31:22 +04:00
2013-04-10 23:51:16 +02:00
2013-04-19 16:21:37 -07:00
2011-03-14 17:37:05 -07:00
2013-03-21 10:52:01 -07:00
2013-04-17 00:08:28 +02:00
2012-12-28 16:42:51 +01:00
2013-02-27 16:29:36 -08:00
2013-04-11 11:06:20 -07:00
2013-03-28 13:19:08 -07:00
2013-04-19 10:15:22 -07:00
2013-01-16 16:53:11 +01:00
2013-04-01 14:30:34 +04:00
2013-03-15 16:18:30 -10:00
2013-04-05 09:02:48 -07:00
2013-03-01 17:36:47 -08:00
2012-12-13 17:00:22 -08:00
2012-06-28 10:14:03 -07:00
2013-03-28 10:40:15 -07:00
2013-04-12 11:30:11 -04:00
2013-02-28 23:11:47 +01:00
2013-04-12 16:27:49 -07:00
2013-03-28 13:50:52 +01:00
2012-03-03 23:48:57 -08:00
2013-03-29 14:53:34 +01:00