- From: <bugzilla@jessica.w3.org>
- Date: Wed, 11 Aug 2010 19:49:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9628
Alexey Proskuryakov <ap@webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ap@webkit.org
--- Comment #3 from Alexey Proskuryakov <ap@webkit.org> 2010-08-11 19:49:27 ---
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".
--
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 Wednesday, 11 August 2010 19:49:29 UTC