Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: nodejs/node-v0.x-archive
base: 1d794ec43e5a
Choose a base ref
...
head repository: nodejs/node-v0.x-archive
compare: 01e29202193c
Choose a head ref
  • 1 commit
  • 2 files changed
  • 1 contributor

Commits on Apr 22, 2013

  1. 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.
    @isaacs
    isaacs committed Apr 22, 2013
    Copy the full SHA
    01e2920 View commit details
    Browse the repository at this point in the history