814 2004-06-27 21:33:40 +0000 Misleading error message with invalid HTTP charset parameter 2009-02-26 10:37:22 +0000 1 1 1 Unclassified CSSValidator Other CSS Validator Other other RESOLVED FIXED http://lduskins.net/ P2 normal --- 1 reeb ot www-validator-cvs oldest_to_newest 2052 0 reeb 2004-06-27 21:33:40 +0000 http://jigsaw.w3.org/css-validator/validator?uri=http://lduskins.net/ i think this is bug :( same things with css: http://jigsaw.w3.org/css-validator/validator? uri=http://lduskins.net/ & http://jigsaw.w3.org/css-validator/validator? uri=http://lduskins.net/skins/classic/classic.css :( 2053 1 ville.skytta 2004-06-28 01:39:53 +0000 Apart from the "Please, validate your XML document first!" message being somewhat misleading, I see no bug here. http://lduskins.net/ has a bug though, the response contains a Content-Type HTTP header with an invalid charset value (note the "." before "win"): $ HEAD http://lduskins.net/ | grep Content-Type Content-Type: text/html; charset=.win-1251 Your CSS example does not have the same problem: $ HEAD http://lduskins.net/skins/classic/classic.css | grep Content-Type Content-Type: text/css Leaving open for comments about improving the error message. 18058 2 thomas 2007-12-13 12:32:59 +0000 I have a similar issue, when using IIS and Classic ASP, where Charset is returned in caps. Is this "attribute" supposed to be case-sensitive? 23800 3 ylafon 2009-02-17 16:22:02 +0000 For CSS files, it now says ".UnsupportedEncodingException: .win1251" The message may be prettier, but at least the explanation of the issue is there.