This reverts commit 9f92332.

Instead, just perform a request.

Conflicts:

	lib/node-http-proxy/http-proxy.js

…e@0.6.x

… longer set synchronously

…-https-to-https.js, lines 37 and 46

…iscover when you run into it. If there was an error, people would search for the error text, but there isn't.

proposed doc addition for http-party#180

[docs] improved grammar

[docs] Making README links consistent with latest project structure.

…mistake.

…to be consistent with `proxyError` events.

…t be a string, not undefined' in certain cases

Mention Harmon used for response modifications in the readme

…ce to reduce listener churn and reference counts.

Fixing a bug that generates an unexpected TypeError

Change the emitter of the `proxyResponse` event

Fix for slab buffer retention, leading to large memory consumption

Since the proxy requests comes from NodeJS's HTTP 1.1 request client, a
backend server may default to setting Connection: keep-alive in its
response. However, the real HTTP 1.0 client may not be able to
handle that.

Force HTTP 1.0 client's to Connection: close, unless the client
explicitly supports keep-alive.

Correct keep-alive responses to HTTP 1.0 clients

The headers in the 'handshake' event were not written to the socket, the client received data but not the headers.

Using only SNICallback to create a HTTPS / TLS server is bad. It means all non SNI clients can't do anything because there are no certs.

in v0.10 of node TLS server was updated to throw if you forgot to supply certs.

Which means that every HTTPS server needs to supply certs as a fallback for when SNI is not available.

 - closes http-party#399

Pass default certs to SNICallback example