Pragma: header and preventing caching in general (Reinier Post)
Date: Wed, 1 Jun 1994 16:01:41 +0200
Message-id: <>
Precedence: bulk
From: (Reinier Post)
To: Multiple recipients of list <>
Subject: Pragma: header and preventing caching in general
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
X-Mailer: ELM [version 2.4 PL23]
X-Mailer: ELM [version 2.4 PL23]
Two questions to those (Ari et al.) who are working on proxy and caching:

Recently, a new HTTP request header was introduced (Pragma: no-cache)
to make it possible for clients to ask intermediaries to refrain from caching
a document.  As I gathered from the discussion, its main purpose was to make
the Refresh function of clients actually refresh the document by causing it
to refresh any intermediate caches also.

Apparently, the name of this header doesn't match its intended
usage.  What you want is a request for the cache server to refresh the
document in cache, instead of bypassing the cache altogether.  My question:
don't we rather need a Pragma: refresh header?

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?  (It's not yet there on

).  Maybe with an HTML equivalent, too.

Reinier Post
a.k.a. <A HREF="">me</A>