W3C home > Mailing lists > Public > www-validator@w3.org > December 1999

XHTML Support is Broken (was: Fwd: W3C Validator Error)

From: Terje Bless <link@tss.no>
Date: Mon, 6 Dec 1999 00:04:53 +0100
Message-Id: <199912052302.AAA29899@vals.intramed.rito.no>
To: W3C Validator <www-validator@w3.org>
cc: Bjoern Hoehrmann <derhoermi@gmx.net>, Gerald Oskoboiny <gerald@w3.org>
On 05.12.99 at 21:51, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

>>Error: could not get "/TR/xhtml1/DTD/strict.dtd" from "www.w3.org"
>>(reason given was "Found")
>'Found' is Status 200, so wheres the problem?

"Found" is 302; "OK" is 200.

The Validator (or rather nsgmls) is probably barfing on the 302 which
www.w3.org is returning; probably related to the XHTML 1.0 recall and
imminent rerelease. I don't /think/ this is related to the latest code
changes in the "check" CGI program, but you never know.

I don't have time to cook up a fix right now -- and I'd have to wait for
Gerald in any case -- but if he doesn't get to it by tomorrow night I'll
try to make time to look at possible fixes (if there are any that don't
involve recompiling nsgmls or modifying www.w3.org configuration!) so at
least those running local copies can get XHTML support back.

As a wild guess, the URI that validator.w3.org has for the XHTML Strict DTD
is wrong and www.w3.org is redirecting requests to the right location. If
that's the case, it's a simple matter of pointing the validator at the
right URI. That could be the aftermath of the addition of configuration
files in the Validator (it may for some reason be unable to parse a config
file and is fetching all DTDs remotely), but I don't think that change has
landed on the live site yet.
Received on Sunday, 5 December 1999 18:03:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:58:15 UTC