This makes the https-over-http proxy work when strictSSL is turned on. In v0.8.4, we fixed a bug where an otherwise valid cert would be accepted for a host that was not listed in the CN or subjectaltnames sections of the certificate. However, this breaks proxying, because you want to accept the cert if it comes from the origin server, not tested against the proxy's hostname. This fixes npm/npm#2719
A test for #289
This is a bug resulting in getting UTF-8 mangled data in a callback when explicitly setting an encoding to 'ascii' or 'binary'.
Seems to work as expected
Like in node.js print options if NODE_DEBUG contains the word request
Also remove parser error listener when finished
Fix #206 Change HTTP/HTTPS agent when redirecting between protocols
documenting additional behavior of json option
Boundary begins with CRLF?
This requires a bit of non-DRY repetition, and a change to the way that the poolKey is generated.
Remove stray `console.log()` call in multipart generator.
Composability updates suggested by issue #239
OAuth Authorization header contains non-"oauth_" parameters
…y but we should defer this restriction for as long as possible.
…y.js to verify