867878 - X-UA-Compatible Lowercased

Status: RESOLVED INVALID

(Core :: Networking: HTTP, defect)

Description

[Lee Wilson]

Attachment: snapshot.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:21.0) Gecko/20100101 Firefox/21.0
Build ID: 20130425162858

Steps to reproduce:

1)  Apache 2.4.3 server sends HTTP Header - 
Configured in Apache vhosts as:  Header set X-UA-Compatible "IE=Edge,chrome=1"
2)  Inspect response headers using native developer tools, header name shows as lowercase
3)  Inspected response using Firebug and see same problem
3)  Validated with same test against Firefox 20 - Problem does not occur


Actual results:

The X-UA-Compatible header shows with correct value, but the Header name value is shown as lowercase.


Expected results:

The X-UA-Compatible header shows with correct name and value as it is being sent from the server.

Comment 1

[Patrick McManus [:mcmanus]]

thanks for logging this.

while I'm not sure what causes that for x-ua-compatible off the top of my head, but we do case normalization for certain headers and its perfectly valid because field names are case insensitive. (rfc 2616 section 4.2)

Comment 2

[Joó Ádám]

Yeah, it was really nice to spend a couple of hours debugging my Nginx configuration because the developer tools, which is supposedly there to help me

1) does not display header field names the way it receives them,
2) neither does it normalize them consistently,

but displays them in whatever case they happen to find themselves after being abused by some evidently **** up architecture up there, which I can only suppose is the result of the same mentality that resolves bug reports against said inconsistency by basically saying „who cares”.