I seem to be having this problem, not sure what the solution or workaround
is.
I'm writing the head as follows:
response.writeHead (200, {"Content-Type": "text/html",
"Access-Control-Allow-Origin": "fargo.io"});
When it shows up on the client, the header names are lowercased.
Happens in two clients, so I'm fairly sure it's the server doing this.
It doesn't look like this was resolved in 2012.
Help! :-)
Dave
On Tuesday, March 8, 2011 7:43:56 PM UTC-5, 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
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
