isaacs 234fb122bb http client: Ensure socket cleanup on response end ...

If an http response has an 'end' handler that throws, then the socket
will never be released back into the pool.

Granted, we do NOT guarantee that throwing will never have adverse
effects on Node internal state.  Such a guarantee cannot be reasonably
made in a shared-global mutable-state side-effecty language like
JavaScript.  However, in this case, it's a rather trivial patch to
increase our resilience a little bit, so it seems like a win.

There is no semantic change in this case, except that some event
listeners are removed, and the `'free'` event is emitted on nextTick, so
that you can schedule another request which will re-use the same socket.
From the user's point of view, there should be no detectable difference.

Closes #5107

2013-04-02 20:34:08 +04: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

test: Fix debugger repl tests

2013-02-26 16:49:17 -08:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

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 client: Ensure socket cleanup on response end

2013-04-02 20:34:08 +04:00

common.js

test: optionally set common.PORT via env variable

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