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 19821 - Using the Validate by URI fails to find doctype but Validate by Direct Input does
Summary: Using the Validate by URI fails to find doctype but Validate by Direct Input ...
Status: RESOLVED INVALID
Alias: None
Product: Validator
Classification: Unclassified
Component: Parser (show other bugs)
Version: HEAD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-01 18:02 UTC by skube
Modified: 2012-11-06 18:51 UTC (History)
0 users

See Also:


Attachments

Description skube 2012-11-01 18:02:37 UTC
When I try to validate a page, say http://www.gm.ca/gm/english/corporate/about/ourcompany/overview
through the URI tabbed interface, I'll see an error relating to not finding the doctype. However, if I copy the source directly and validate by direct input, I'll see different errors completely.

Should these not be the same exactly?
Comment 1 Ville Skyttä 2012-11-06 18:51:15 UTC
If given the exact same input, then yes. But in practice they're never exactly the same, there are server generated headers and possible content negotiation in the equation when validating by URI etc.

In this case, I bet the document served to the validator by the www.gm.ca server is pretty far from the one you're feeding it with direct input; use the "show source" option to see what the validator received.