Piping a stream to an HTTPS ClientRequest would stall if the request's
write() method returned false; the readable stream would pause and
never resume because the the request would never emit a drain event.
It turns out that the request stream did not listen to the underlying
TLS socket drain event because it was expecting the socket to invoke
its "ondrain" method instead. Now it does.