I just tested this, and it seems it wont touch them. [1] I recall having this issue with S3 not recognizing lowercased content-length header. And explicitly setting the header key as Content-Length fixed it.
[1] https://gist.github.com/4186458 danmilon. On Sun, Dec 2, 2012 at 3:07 AM, Mikeal Rogers <[email protected]> wrote: > by default node.js sends headers in lowercase. by spec, HTTP headers are > caseless. if someone does not treat them that way you email them and ask them > why they suck at HTTP. > > On Dec 1, 2012, at December 1, 20124:50 PM, Dan Milon <[email protected]> > wrote: > >> AFAIK outgoing headers are not lowercased. Do you have a test case? >> >> danmilon. >> >> On Sat, Dec 1, 2012 at 10:01 PM, Cristian Bullokles >> <[email protected]> wrote: >>> Looks like this change stills in v0.8.15 of node.js, I'm trying to >>> authenticate to an OAuth provider and I've the same problem. My provider is >>> not able to recognize the authorization header. >>> Do we have a fix for that issue? >>> >>> >>> >>> On Tuesday, March 8, 2011 9:43:56 PM UTC-3, Eran Hammer-Lahav wrote: >>>> >>>> A recent update changed how client request headers are sent to force all >>>> headers to lowercase. This is causing problems with some well-established >>>> (and non-compliant) servers which look for specific case-sensitive >>>> formatting. My application is now failing on both the 'Authorization' and >>>> 'Cookie' headers with some large providers. >>>> >>>> I see the value in changing incoming headers to lowercase, but it would be >>>> better to leave outbound headers alone and allow applications to set the >>>> headers to the exact format expected by the server in case of a misbehaving >>>> provider. >>>> >>>> Can this be changed back? >>>> >>>> EHL >>> >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: >>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
