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 814 - Misleading error message with invalid HTTP charset parameter
Summary: Misleading error message with invalid HTTP charset parameter
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: Other (show other bugs)
Version: CSS Validator
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL: http://lduskins.net/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-27 21:33 UTC by Zaykovskiy Andrey
Modified: 2009-02-26 10:37 UTC (History)
0 users

See Also:

Attachments

Comment 1 Ville Skyttä 2004-06-28 01:39:53 UTC 
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.
Comment 2 Thomas Kj 2007-12-13 12:32:59 UTC 
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?
Comment 3 Yves Lafon 2009-02-17 16:22:02 UTC 
For CSS files, it now says ".UnsupportedEncodingException: .win1251"
The message may be prettier, but at least the explanation of the issue is there.