when setting defaults, the wrapper adds the jar method assuming it has the same signature as get, meaning undefined is passed into initParams, which subsequently fails.  now passing jar function directly as it has no need of defaults anyway seeing as it only creates a new cookie jar
Added test to illustrate #321
Added *src* stream removal on redirect. #321
Do not try to remove listener from an undefined connection

See issue #325
Merge pull request #326 from CartoDB/removeListener

Do not try to remove listener from an undefined connection
Merge pull request #322 from alexindigo/master

Fix + test for piped into request bumped into redirect. #321
New version in npm.
Rolling trunk version.
Adding url to redirect error for better debugging.
Better debugging of max redirect errors.
Merge pull request #320 from redbadger/master

request.defaults() doesn't need to wrap jar()
Fix #296 - Only set Content-Type if body exists
fixup aws function to work in more situations
added short blurb on using aws
Merge pull request #343 from nathan-lafreniere/master

Allow AWS to work in more situations, added a note in the README on its usage
switch to a case insensitive getter when fetching headers for aws auth signing
Merge pull request #332 from Marsup/issue-296

Fix #296 - Only set Content-Type if body exists
Emit errors for anything in init so that it is catchable in a redirect.
fix bug

if you delete the body, you should also delete any existing content-type and content-length, otherwise you're sending erroneous values: e.g. content-type form-encoded, content-length 1415, empty body 
Merge pull request #355 from azylman/master

stop sending erroneous headers on redirected requests