Re: Caching and metainformation

• Mail folder: WWW Talk Jan 94-present
• Next message: Kevin Altis: "Re: Problem with "~user/file.html""
• Previous message: Kevin Altis: "SGML parsing, moving between formats"
• Maybe in reply to: Paul Burchard: "Re: Caching and metainformation"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 21:16:44 --100
Message-id: <m0pWW2W-000439C@ibeam.intel.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: altis@ibeam.jf.intel.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: altis@ibeam.jf.intel.com (Kevin Altis)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Caching and metainformation
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 833

At  3:38 PM 2/15/94 +0000, Paul Burchard wrote:
>altis@ibeam.jf.intel.com (Kevin Altis) writes:
>> In the cases of documents that are candidates to cache, we
>> need to explicitly state which HTTP metainformation
>> "fields" a server needs to send in order for the document
>> to be cached correctly.
>
>Could you clarify how this would affect POST forms?  Are you
>suggesting that POST forms will have to include explicit
>metainformation to prevent themselves from being cached (which would
>seem to be undesirable in most cases)?

A Caching/Proxy server might cache a FORM coming from a server, but would
never cache the FORM being POSTed to that server. Perhaps, caching FORMs
from a server is always a bad idea, in which case, a tag in the HEAD area
needs to identify that a FORM shouldn't be cached, say Expires: always.

ka