set it as `options.defaultRequest` instead. That is just going to confuse people. Not sure what I was thinking there.
Allow users to intercept and perform influence the redirection themselves. This adds a `makeRequest` option that can be used to do just that. For now, my plan is to leave it undocumented, because I want to get a release out, and don't want to commit to this API decision just yet. Specifically, I want make some progress on #19, and #12 before committing to exactly how it will behave.
streams in node v0.8 have some interesting issues. Mainly you must not defer consuming them with a `stream.on('data', ...)` handler, or you will miss data (there doesn't seem to be any buffering). This is problematic for our test suite which use promises (which will defer until next tick once resolved). This change changes the `concatJson` utility method to consume the result stream immediately, and resolve the promise with parsed result. There are still https issues in node 0.8, so I'm using semver to skip those for now.
adds James Talmage to the list of contributors adds urls for the github repo "homepage" and issues lists to package.json.