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

..

addons

test: modify async native test.js to test for #4820

2013-02-21 13:14:07 -08:00

disabled

Merge remote-tracking branch 'ry/v0.8' into master

2013-02-18 10:21:08 -08:00

fixtures

tls: expose SSL_CTX_set_timeout via tls.createServer

2013-03-26 01:37:49 +01:00

gc

test: fix up weakref.cc after v8 api change

2013-03-20 01:53:34 +01:00

internet

DNS: Support NAPTR queries

2013-03-06 14:31:22 +04:00

message

test: Fix message/error_exit

2013-04-05 11:32:33 -07:00

pummel

tls: expose SSL_CTX_set_timeout via tls.createServer

2013-03-26 01:37:49 +01:00

simple

http: Don't try to destroy nonexistent sockets

2013-04-22 10:38:14 -07:00

common.js

test: optionally set common.PORT via env variable

2013-03-02 19:09:39 +01:00