Closed
Bug 271888
Opened 20 years ago
Closed 20 years ago
charset parameter using quoted-string ignored
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 244964
People
(Reporter: nirs, Assigned: darin.moz)
References
()
Details
Attachments
(1 file)
878 bytes,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When using charset parameter using quoted-string, Mozilla/Firefox ignore the charset and use the charset defined in the head meta tag. Example: Content-Type: text/html; charset="iso-8859-8" According to href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7, media type e.g. text/html can use parameters using format specified in http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6. The quoting is not needed in this case, but this seems to be valid HTTP 1.1 content type declaration. * IE 6.0 also ignore such charset * Safari respect it * W3C HTML validator respect this charset Compare with same testcase using token: 'Content-Type: text/html; charset=utf-8'. Here Mozilla works fine. http://nirs.dyndns.org/cgi-bin/token.cgi Reproducible: Always Steps to Reproduce: 1. Visit testcase url Actual Results: Page rendered using charset defined in head meta tag Expected Results: Page should render in charset defined in HTTP header Content-type
Reporter | ||
Comment 1•20 years ago
|
||
The source of my Python cgi testcase.
Comment 2•20 years ago
|
||
*** This bug has been marked as a duplicate of 244964 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
V/dupe
Status: RESOLVED → VERIFIED
QA Contact: core.networking.http → benc
You need to log in
before you can comment on or make changes to this bug.
Description
•