On Tue, Mar 8, 2011 at 7:43 PM, Eran Hammer-Lahav <eran <at> hueniverse.com> 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.

Out of curiosity can you tell us who they are? Perhaps a little name and shame can help -- after all, this is a pretty egregious oversight.

 

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

--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.