Re: I want have "Last-modified:" in HTTP/1.0 headers
Marc VanHeyningen <mvanheyn@cs.indiana.edu>
From: Marc VanHeyningen <mvanheyn@cs.indiana.edu>
To: www-talk@nxoc01.cern.ch
Subject: Re: I want have "Last-modified:" in HTTP/1.0 headers
In-reply-to: Your message of "Fri, 12 Nov 1993 11:40:01 PST."
<93Nov12.114016pst.2445@spoggles.parc.xerox.com>
Date: Fri, 12 Nov 1993 15:43:33 -0500
Message-id: <5654.753137013@frilled.cs.indiana.edu>
Sender: mvanheyn@cs.indiana.edu
Thus wrote: Steve Putz
>Guenther,
>
>Beware of HTTP servers that are really *gateways* to information you
>may not want to cache. I have two such servers:
>
> http://pubweb.parc.xerox.com/map
>and
> http://web2.xerox.com/digitrad
>
>Both are front ends to large databases where it makes little sense to
>cache. However both servers also have a small and fairly static
>hierarchy of HTML documents as well, under:
>
> http://pubweb.parc.xerox.com/hypertext
>and
> http://web2.xerox.com/docs
>
>Can your cache server be configured to know the difference?
Short of having every example of a gateway coded in, how could a cache
server possibly tell the difference?
Rhetorical question. Answer: The Expires: header. It's the
responsibility of the server to make available an indication of how
long that information will remain "current".
- Marc
--
Marc VanHeyningen mvanheyn@cs.indiana.edu MIME, RIPEM & HTTP spoken here