W3C home > Mailing lists > Public > public-qa-dev@w3.org > February 2005

Checking Recursion (was: validator/httpd/cgi-bin check,1.391,1.392)

From: Terje Bless <link@pobox.com>
Date: Sat, 5 Feb 2005 22:41:10 +0100
To: QA Dev <public-qa-dev@w3.org>
Message-ID: <b02010503-1037-A71E7A5277BE11D9B94E000D9348908C@[193.157.66.142]>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

>I am not fond of this introduction of experimental HTTP headers,

_Private_ HTTP header fields; they're not supposed to be meaningful outside of
the instance where /check is talking to itself. I dunno. The way we're using
them I have few qualms about it.


>I think we should rather check the URL of the target document against the
>check URL.

Too many pitfalls to implement reliably, alas. That's what I started out with,
but ended up rejecting it for this method.


>I further think that refusal to check the validator output is a bad
>idea (we, after all, link to that in the results page), so the default
>should be to limit two or at least one recursion.

Well, there's a distinction between what we ship as a default and what we
configure our installation on v.w3.org to do. The default as shipped should be
zero because we want to err on the side of caution, but v.w3.org should be
able to check itself and qa-dev should probably allow infinite recursion.

- -- 
"Fly it until the last piece stops moving..."

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.2.2

iQA/AwUBQgU9daPyPrIkdfXsEQIXkQCeMi+bpfmuZGR6Kg/e5+12n4B8r/sAn3tm
NAOOvP/5O3BFimBAbukm8isT
=qXn5
-----END PGP SIGNATURE-----
Received on Saturday, 5 February 2005 21:41:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 August 2010 18:12:45 GMT