W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1998

http acceleration and Date headers

From: Andrew Daviel <andrew@andrew.triumf.ca>
Date: Sun, 8 Mar 1998 21:44:57 GMT
To: squid-users@nlanr.net, http-wg@cuckoo.hpl.hp.com
Message-Id: <Pine.LNX.3.95.980308133109.29070A-100000@andrew.triumf.ca>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5439

I have been doing a survey of clock accuracy
(http://vancouver-webpages.com/time/) and have  found that, while the
majority of Web server clocks (as derived from the http Date header)
are very accurate, a few  are way off.

I then wondered what the effect was of running an http accelerator (Squid
in httpd_accel mode, for instance) and tried it. It seems that the
Server header is unmodified, but that the Date header remains set at
whatever the origin server said until someone does an unconditional GET
(shift-reload in Netscape) (or presumeably until the original page is

I can't tell (as far as I know) if this is actually the reason for
seeing clock errors.

I wondered if this was the way that httpd accelerators were intended to

Andrew Daviel
Vancouver Webpages & TRIUMF
Received on Monday, 9 March 1998 04:04:43 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:04 UTC