We've had issues where we need to send Content-Length as a header, rather than content-length; when content-length lowercase is in the request, the request fails.
I've put some more checks around content-length so that request doesn't do this if we've already worked out Content-Length
I thought it was part of the HTTP spec that headers we in fact uppercase? According to RFC2616?
Made it so that if we pass in Content-Length or content-length in the…
… headers, don't make a new version
Hi Mikeal, thanks for merging so quickly.
Is this likely to be released to npm soonish? Or would I be better pointing my package.json file to github for me to access this change?
umn.... soon :)