Re: WWW Proxy information
altis@ibeam.jf.intel.com (Kevin Altis)
Errors-To: listmaster@www0.cern.ch
Date: Mon, 2 May 1994 00:38:03 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <m0pxk29-0003V3C@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: WWW Proxy information
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset="us-ascii"
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Mime-Version: 1.0
At 3:50 PM 5/1/94 -0500, Paul Burchard wrote:
>> If you have concerns about application level proxies in
>> general or our solution specifically, then please raise
>> them on this list rather than emailing me directly so that
>> we can all participate in the discussion.
>
>
>Just a quick question -- could you clarify if authors of interactive
>pages (POST FORMs) need to do anything in order to prevent unintended
>caching in this system? Or is this handled automatically? Thanks!
The FORM itself could be cached depending on the settings on the proxy
server for a site as could the results, but in general, the *results*
wouldn't be cached because results wouldn't have Last-modified or Expires
meta-information and the default caching time for HTTP results without
those meta-fields is 0. I'm currently experimenting with a default
expiration of 15 minutes to an hour or so, to see if it makes a difference
to users.
ka