Re: I want have "Last-modified:" in HTTP/1.0 headers

• Mail folder: WWW Talk Oct 93-present
• Next message: Steve Putz: "Re: I want have "Last-modified:" in HTTP/1.0 headers"
• Previous message: Marc VanHeyningen: "Re: I want have "Last-modified:" in HTTP/1.0 headers "
• In-reply-to: Steve Putz: "Re: I want have "Last-modified:" in HTTP/1.0 headers"

Errors-To: sanders@bsdi.com
Errors-To: sanders@bsdi.com
Message-id: <199311122053.OAA12776@austin.BSDI.COM>
X-Authentication-Warning: austin.BSDI.COM: Host localhost didn't use HELO protocol
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.
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Fri, 12 Nov 1993 14:53:44 -0600
From: Tony Sanders <sanders@bsdi.com>

> Beware of HTTP servers that are really *gateways* to information you
> may not want to cache.  I have two such servers:
The way to solve this is to #1 run an HTTP/1.0 server and #2
define a mechanism so that the client/gateway can know this,
perhaps using the already defined Expires: header.  At any rate,
it's the job of the server to contain this information.

That said, I see no reason not to cache at least the map server.
If it's not used much the cache should expire rapidly.

--sanders