W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

[Bug 18521] Spec is unclear about lower-casing content types

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Sep 2012 20:12:25 +0000
Message-Id: <E1T9iR7-00033S-9P@jessica.w3.org>
To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18521

Arun <arun@mozilla.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #3 from Arun <arun@mozilla.com> 2012-09-06 20:12:24 UTC ---
In the spec., I defer to RFC2616, asking the parser to parse it in accordance
with the definition of type and subtype tokens.

RFC2616 says:

The type, subtype, and parameter attribute names are case-insensitive.
Parameter values might or might not be case-sensitive, depending on the
semantics of the parameter name.

Thus, TEXT/HTML is equivalent to text/html.

This isn't a bug, but an implementation quirk.  I don't think we need further
spec. guidance on this issue.  In fact, I think it places an emphasis on
authors to coin the type string with some diligence.  Authors get back what
they ask for.

Marking invalid.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 6 September 2012 20:12:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:54 GMT