pause and resume should act on response instead of request
Making request really smart about pipeing to itself so that we can do simple proxy cats
Rolling version since master right now has some pretty hot new code in it.
Merge pull request #31 from tobowers/master

Error on piping a request to a destination
The "end" event that was supposed to be emitted to fix a core bug in NodeJS wasn't fired because it wasn't emitted on the response object.

I encountered this problem when trying to fetch https://profiles.google.com/VoxPelli through JSDom. I tracked it down to being that the response object in this file only emitted "data"-events and no "end"-events. The change here fixed that.

(I hope the bonus spelling correction of "because" is okay as well :) )
Merge pull request #35 from voxpelli/patch-1

The "end" event isn't emitted for some responses
Rolling version.
Fixing bug in forwarding with new pipes logic.
Fixing big bug in forwarding logic.
Added timeout option to abort the request before the response starts responding
corrected spelling error in README
Merge pull request #45 from mbrevoort/master

Added timeout option
Fixing for node http client refactor.
Merge branch 'master' of github.com:mikeal/request
New fs.ReadStream handling hotness.
Adding pipe support to HTTP ServerResponse objects.
Setting proper statusCode.
Adding test for pipeing file to disc.
Pumping version.
Adding reference to Request instance on response to make it easier on inline callbacks. fixes #43.