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 749 - Fatal errors trigger XHTML output for XML output method
Summary: Fatal errors trigger XHTML output for XML output method
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: Other other
: P2 normal
Target Milestone: 0.7.0
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL: http://validator.w3.org/check?uri=htt...
Whiteboard:
Keywords:
Depends on:
Blocks: 856
  Show dependency tree / graph
 
Reported: 2004-05-27 20:04 UTC by Bj
Modified: 2005-02-04 19:46 UTC (History)
0 users

See Also:

Attachments

Description Bj 2004-05-27 20:04:08 UTC 
E.g.

http://validator.w3.org/check?uri=http://www.w3.org/robots.txt;output=xml

in case of fatal errors such as an illegal mime type the validator returns an 
XHTML document even for the XML output method. It should return this 
information encoded in the XML format.
Comment 1 Ville Skyttä 2004-10-16 22:14:52 UTC 
Hm, I guess we should templatize the XML (and EARL and n3) outputs too.

The current dir structure doesn't provide a separate dir for these, should it?
Alternatively, we could do $template.{xml,earl,n3}.tmpl or something like that.

While at it, perhaps it would be a good idea to switch to RFC3066 formatted
language identifiers (en-us and friends) in language specific dir names to avoid
unnecessary mappings to the Unixish (?) (en_US and friends) ones?
Comment 2 Terje Bless 2005-02-04 19:46:06 UTC 
Fixed. Fatal errors now output the correct format, noting the fatal error,
and refers to interactive mode in the web interface to determine the exact
nature of the problem (to avoid arbitrary HTML in the XML output, e.g.).