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 5554 - Cannot validate web pages with content-type headers of text/x-server-parsed-html
Summary: Cannot validate web pages with content-type headers of text/x-server-parsed-html
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: HEAD
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2008-03-10 18:11 UTC by Jeff Connelly
Modified: 2008-04-17 11:58 UTC (History)
0 users

See Also:


Description Jeff Connelly 2008-03-10 18:11:26 UTC
I'm trying to validate this web page:

However, the server (incorrectly, I believe, due to server misconfiguration) sends a Content-Type header with a value of "text/x-server-parsed-html" instead of the usual text/html, so the validator cannot validate it. The error message given is:

Sorry, I am unable to validate this document because its content type is text/x-server-parsed-html, which is not currently supported by this service.

The Content-Type field is sent by your web server (or web browser if you use the file upload interface) and depends on its configuration. Commonly, web servers will have a mapping of filename extensions (such as ".html") to MIME Content-Type values (such as text/html).

That you received this message can mean that your server is not configured correctly, that your file does not have the correct filename extension, or that you are attempting to validate a file type that we do not support yet.

None of the options in the validator could override this error and allow the page to be validated. 

Could we perhaps have a dropdown box to manually specify a Content-Type, if the server incorrectly specifies it, in order to proceed with validation? Similar to how the validator can manually accept an explicit "Encoding" and "Doctype" type.
Comment 1 Olivier Thereaux 2008-04-17 11:58:35 UTC
I think it is sound that the validator only accepts reading content served with media types it can handle.

I would suggest fixing the server misconfiguration and/or using the alternate input methods to the validator.