W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2010

[Bug 9628] Algorithm for detecting the charset="" parameter.

From: <bugzilla@jessica.w3.org>
Date: Sat, 13 Nov 2010 17:34:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PHK03-0004AL-PG@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9628

Julian Reschke <julian.reschke@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #15 from Julian Reschke <julian.reschke@gmx.de> 2010-11-13 17:34:47 UTC ---
(In reply to comment #3)
> Safari's (closed source) network back-end parses Content-Type for charset in a
> manner that's different from both RFC2616 and the current HTML5 spec. We also
> have a separate parser in WebKit that's used in a limited set of circumstances
> (only for XMLHttpRequest.overrideMimeType and for correcting a MIME type set
> via XMLHttpRequest.serRequestHeader).
> 
> But I am no aware of any evidence against following RFC2616 to the letter when
> getting charset out of Content-Type.
> 
> >  Content-Type: text/plain; charsetfoo=bar; charset=UTF-8
> 
> Also, this algorithm fails to ignore charset in "Content-Type: text/plain;
> foocharset=UTF-8".

Indeed, even after the change.

Re-opening.

-- 
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, 13 November 2010 17:34:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 13 November 2010 17:34:54 GMT