Re: Private Data Caching Pragma info

Blue Lang wrote:

> From what I understand, I (well, the developers) should be able to mark
> all of the outgoing html with Cache-Control:private, and avoid having any
> sepc-compliant cache hold a copy of the data. This does not count for
> browsers, which do whatever they want.

Correct.

Cache-Control: private makes the content uncachable by shared caches
only.

From RFC2616:
   private
      Indicates that all or part of the response message is intended for
      a single user and MUST NOT be cached by a shared cache. This
      allows an origin server to state that the specified parts of the
      response are intended for only one user and are not a valid
      response for requests by other users. A private (non-shared) cache
      MAY cache the response.

       Note: This usage of the word private only controls where the
       response may be cached, and cannot ensure the privacy of the
       message content.

--
Henrik Nordstrom
Squid hacker