0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/test
isaacs 01e2920219 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 09:54:04 -07:00
..
addons test: modify async native test.js to test for #4820 2013-02-21 13:14:07 -08:00
disabled
fixtures test: Fix debugger repl tests 2013-02-26 16:49:17 -08:00
gc
internet DNS: Support NAPTR queries 2013-03-06 14:31:22 +04:00
message process: separate nextTick domain logic 2013-02-27 16:37:10 -08:00
pummel test: Pass cli flags in pummel/test-regress-GH-892 2013-03-06 11:44:29 -08:00
simple http: Don't try to destroy nonexistent sockets 2013-04-22 09:54:04 -07:00
common.js test: optionally set common.PORT via env variable 2013-03-02 19:09:39 +01:00