- From: Ari Luotonen <luotonen@netscape.com>
- Date: Wed, 10 Jan 1996 05:32:03 -0800 (PST)
- To: koen@win.tue.nl (Koen Holtman)
- Cc: mogul@pa.dec.com, drtr1@cus.cam.ac.uk, http-caching@pa.dec.com
> >Is this what HTTP/1.0 caches do: keep things for 7 days? Or does > >the practice vary? Any experts out there? > > I believe the practice varies. The CERN cache seems to have the > directive CacheRefreshInterval to specify such an upper bound. The > documenattion file gives > > CacheRefreshInterval * 1 week Both CERN and Netscape Proxies use two parameters; one is the above-mentioned CacheRefreshInterval (max-uncheck in ns-proxy), and CacheLMFactor (lm-factor) which is used to estimate the expiration time by using Last-Modified header. Harvest Cache Daemon and others that I know of use only the CacheRefreshInterval; they lack the lm-factor which is very useful in catching documents for which the default max-uncheck would be too high. Cheers, -- Ari Luotonen ari@netscape.com Netscape Communications Corp. http://home.netscape.com/people/ari/ 501 East Middlefield Road Mountain View, CA 94043, USA Netscape Server Development Team
Received on Wednesday, 10 January 1996 14:02:52 UTC