W3C home > Mailing lists > Public > www-validator-cvs@w3.org > October 2004

[Bug 922] Wrong content-type detected with broken HTTP server

From: <bugzilla@wiggum.w3.org>
Date: Thu, 21 Oct 2004 11:55:15 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1CKbXH-0003d1-ER@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=922





------- Additional Comments From nunoanjos@yahoo.com  2004-10-21 11:55 -------
Now that I think better about it, how can it be possible? At any time, the site
was loaded and correctly shown by a browser. When I saw any page source, the
HTML code is complete, seeming well-interpreted by the browser, and I think the
<head></head> section was processed as well, because the <title></title> tags
were executed (looking at the top of the browser window, there was the title
being shown).

And still, and this same time, the W3C validator gave me two different kinds of
errors, being unable to validate my site. That is what I don't understand. If
the browser was getting the full HTML code and processing it correctly,
shouldn't the W3C validator do the same? I don't know exactly how the validator
works, but I guess it behaves like the browser, parsing line by line, and trying
to find known tags to check if they comply.

If the W3C validator received the same HTML code as the browser, how can the
browser execute it well and the W3C be unable to parse it? Maybe, with the
information given by me, the W3C validator authors could understand better than
I why this happened.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Thursday, 21 October 2004 11:55:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:08 UTC