Re: Pragma: header and preventing caching in general

• Mail folder: WWW Talk Apr 94-present
• Next message: neuss@igd.fhg.de: "Re: meta information "
• Previous message: Michael Mealling: "An Anchor attribute question:"

Errors-To: listmaster@www0.cern.ch
Date: Wed, 1 Jun 1994 16:25:49 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9406011415.AA02375@tommy.informatik.uni-dortmund.de>
Errors-To: listmaster@www0.cern.ch
Reply-To: klute@tommy.informatik.uni-dortmund.de
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Rainer Klute <klute@tommy.informatik.uni-dortmund.de>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Pragma: header and preventing caching in general 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=ISO-8859-1
Content-Type: text/plain; charset=ISO-8859-1
Mime-Version: 1.0
Mime-Version: 1.0
Organization: CS Department, Dortmund University, Germany
Organization: CS Department, Dortmund University, Germany

>The second question: several occasions have arisen in which it would be useful
>for the remote server (not the client) to explicitly indicate that
>the document sent must not be cached.  (For example, the case of WIRED,
>where fragments of copyrighted material are cached, but copyright is not
>on the individual fragments.)  Can I suggest that the Pragma: no-cache header
>is added to the valid HTTP response headers?

Of course you can suggest that, but there is already the Expires: header which
gives the server complete control over when a document should be regarded
out-dated. If only information providers would support that header!

Best regards
Rainer Klute

  Dipl.-Inform.                     IRB  - immer richtig beraten
  Rainer Klute                      EXUG - European X User Group
  Universitdt Dortmund, IRB
D-44221 Dortmund                    Tel.: +49 231 755-4663

        <http://www.informatik.uni-dortmund.de/~klute/>