[Webkit-unassigned] [Bug 32837] Explicit Content-Type value "text/css" changed to "text/html, text/css"

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 21 13:40:06 PST 2009


https://bugs.webkit.org/show_bug.cgi?id=32837





--- Comment #1 from Mark Rowe (bdash) <mrowe at apple.com>  2009-12-21 13:40:06 PST ---
The server is sending two Content-Type headers:

Content-Type: text/html
Content-Type: text/css

RFC 2616 has this to say about the presence of multiple headers with the same
name:

> Multiple message-header fields with the same field-name MAY be present
> in a message if and only if the entire field-value for that header field
> is defined as a comma-separated list [i.e., #(values)].

Since Content-Type’s value isn’t defined to be a comma-separated list the
response headers for this resource appear to be invalid.  That said, we appear
to be handling these invalid headers in a different manner than how Firefox
handles them.  We should look at matching their behavior here.

In the mean time the website could achieve the result they’re after by sending
valid response headers.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list