The number of maxSockets has to be set after the agent is created. Settin

[KimSchneider]

The number of maxSockets has to be set after the agent is created. Setting the property in the constructor does not work.

[jamesonjlee]

this is actually is a feature of node.js core.

https://github.com/joyent/node/blob/v0.4.10/lib/http.js#L1139-1147

unless this is something that would be useful? @dominictarr

[dominictarr]

am yet to confirm the bug this commit fixes. see discussion here: #80

[bluescreen303]

Just ran into this issue
I used setMaxSockets, but all agents report their default (5) instead.
Indeed, it appears the Agent constructor doesn't look at the maxConnections option, but rather uses the global Agent.defaultMaxSockets
So if http-proxy wants to set this, it has to occur after calling the Agent constructor.

[dominictarr]

you where right,

thanks!

[indexzero]

@DrJackal @KimSchneider is actually correct here. @dominictarr +1 to merge this