This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4917 - charset detection in <meta> recognises only lower-case charset=
Summary: charset detection in <meta> recognises only lower-case charset=
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.8.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
: 4953 (view as bug list)
Depends on:
Reported: 2007-08-07 05:38 UTC by Olivier Thereaux
Modified: 2007-12-19 05:53 UTC (History)
1 user (show)

See Also:


Description Olivier Thereaux 2007-08-07 05:38:44 UTC
Reporterd by Ernest Unrau

  <META HTTP-EQUIV="content-type" CONTENT="text/html; charset=ISO-8859-1">

NOT Recognised:
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=ISO-8859-1">

 * check HTTP specification for case-sensitivity
   (I believe there is nothing mentioned precisely, but HTTP is case-sensitive)
 * make the validator's detection less strict
 * throw a warning if loose detection caught improper construct
Comment 1 Olivier Thereaux 2007-08-16 23:24:21 UTC
*** Bug 4953 has been marked as a duplicate of this bug. ***
Comment 2 Holger Th 2007-09-08 17:05:48 UTC
This is true not only for charsets specified via the <meta/> element but as well for those specified within HTTP headers. (Content-Type: text/html; charset=utf-8 is fine, while Content-Type: text/html; Charset=utf-8 is not.) Hope this isnt too obvious to be pointed out here.
Comment 3 Olivier Thereaux 2007-09-20 22:59:25 UTC
I reported a bug to LWP, arguing that this module, responsible for the parsing of headers, should make sure it normalizes the case:

The author of HTML::Encoding, which is used by the validator, actually thinks this is not LWP's responsibility and ack'd the bug report:
Comment 4 Olivier Thereaux 2007-12-19 05:53:15 UTC
a new version of the HTML::Encoding library fixes this issue:

tested on the dev server, I am updating the production service with the new library and closing this bug.