[Bug 7549] define how to parse a MIME type

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7549


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

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




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-09-19 10:43:25 ---
It turns out that since HTTP doesn't actually define this (you have to read
between the lines or apply "common sense" to get an idea of how to parse MIME
types, and error handling isn't defined at all), different parts of the
platform have different requirements for how to handle MIME types. For example,
"text/javascript;" (with the semicolon) is not a match in <script type="">, but
"text/html;" is considered an HTML file, despite this MIME type not matching
the grammar in the HTTP spec.

I added text to handle trimming spaces in <script type>. I haven't done
anything for general MIME type handling. I think this is probably something for
MIMESNIFF, since I doubt the HTTPWG will be fixing HTTPbis to define this.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 19 September 2009 10:43:35 UTC