[5274] in www-talk@info.cern.ch
Re: Caching Servers Considered Harmful (was: Re: Finger URL)
daemon@ATHENA.MIT.EDU (John Labovitz)
Mon Aug 22 23:26:21 1994
Date: Mon, 22 Aug 1994 22:27:31 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: johnl@ora.com
From: John Labovitz <johnl@ora.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
[Martijn Koster <m.koster@nexor.co.uk>]
> Just wondering -- do you specify a Expired header for that file,
> indicating it expires daily? If so any cache that doesn't honour it is
> broken. If you don't, then what do you expect?
I just looked through the NCSA httpd source code and found
no way to specify an Expires: header for a file. If this
was a CGI script, I know I could add one myself, but how
do I tell the server to send an Expires: header for an
ordinary HTML or GIF file?
I realize this is getting off track, but it'd be nice to
be able to specify HTTP headers for random files. For the
Unix environment, perhaps file `foo.html' could have an
associated `foo.html.hdr' file that the HTTP server knows
to look for, and adds any headers found there (like Expires).
This would also be a solution to the problem of moved files
-- if I rename `foo.html' to `bar.html', then `foo.html.hdr'
could contain `Location: bar.html' (is that right?), without
having to modify httpd's config file.
--
John Labovitz
Global Network Navigator <http://gnn.com/>
O'Reilly & Associates, Sebastopol, California, USA (+1 707 829 0515)
