mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
01e2920219
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. |
||
---|---|---|
.. | ||
addons | ||
disabled | ||
fixtures | ||
gc | ||
internet | ||
message | ||
pummel | ||
simple | ||
common.js |