W3C home > Mailing lists > Public > www-validator-cvs@w3.org > September 2007

[Bug 4998] Validator sometimes uses cached content (cache-control header on requests would be useful)

From: <bugzilla@wiggum.w3.org>
Date: Mon, 03 Sep 2007 01:23:38 +0000
CC:
To: www-validator-cvs@w3.org
Message-Id: <E1IS0fC-0004dD-96@wiggum.w3.org>

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





------- Comment #1 from ot@w3.org  2007-09-03 01:23 -------
Could you give a practical test case where the current behavior of the
validator is problematic?

As far as I can tell:

* the validator does not use a cache for the resources it checks

* I am assuming that the problem you describe comes from having a caching proxy
between the client (the validator) and the server, and that the cache, when
receiving the request from the validator, does not validate the freshness of
its cached version, which seems rather wrong. Requests with "Cache-Control:
max-age=0" might help per section 13.1.6 of RFC 2616, but if the cache is
misbehaving, it's not even a certainty...
Received on Monday, 3 September 2007 01:23:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:54:59 GMT