W3C home > Mailing lists > Public > www-validator-cvs@w3.org > June 2004

[Bug 801] Improved error message for HttpInvalidValueException

From: <bugzilla@wiggum.w3.org>
Date: Sun, 20 Jun 2004 12:49:55 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1Bc1lj-0008Tw-KV@wiggum.w3.org>

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





------- Additional Comments From ville.skytta@iki.fi  2004-06-20 08:49 -------
The markup validator does indeed "accept" charset:utf-8 in the sense that it
won't bail out if it is present in the Content-Type header.  But it means no
more than exactly that.

As far as the markup validator is concerned, "charset:utf-8" in the Content-Type
header does not mean that the character set of the document is utf-8, it just
means that there is a parameter without a value named "charset:utf-8" in the
header.  Technically, that is somewhat incorrect and the markup validator could
abort as well, because the colon (":") is not allowed in parameter names, ie.
"tokens".
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6
http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2

An possible fix for the CSS validator would be to print the value of the content
type it treats as invalid in the error message, or just skip it silently like
the markup validator does.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Sunday, 20 June 2004 08:49:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:06 UTC