check for req.chunkedEncoding rather than req.useChunkedEncodingByDefault

[spalger]

When investigating why connections were being created and destroyed constantly I noticed that forever-agent looks at the request's useChunkedEncodingByDefault property rather than it's chunkedEncoding property, which seems to actually say if the request is chunked or not. Is there a reason for this?

In this screenshot you can see:

• there are 9 free sockets available
• there are 10 total sockets open
• the request is not chunkedEncoded
• it still creates a new socket

[spalger]

Did not realize that this method is called within http.request(). I think that means that I would have to set the content-length header in the call to http.request() in order to tell ForeverAgent that I will not be using chunked encoding, and it can therefore draw from the connection pool.