[varnish] Re: Default behaviour with regards to Cache-Control

[Ricardo Newbery]

On Feb 13, 2009, at 4:54 AM, Dag-Erling Smørgrav wrote:

> Ole Laursen <olau at iola.dk> writes:
>> I looked up private here
>>
>>  http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
>>
>> and it says
>>
>>    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
>
> Varnish is not a shared cache, it's a surrogate (not covered by  
> RFC2616)
>
> DES


Speaking of which...

It would be super handy if Varnish supported Surrogate-Control.  I  
sympathize with the Varnish developers who feel that everything can be  
done in vcl but some of us really do need the backend to control the  
surrogate cache behavior on a more granular level.

Ric