[varnish] Re: Cacheability - changed in Varnish 2?

[Ricardo Newbery]

On Jan 29, 2009, at 12:34 AM, Poul-Henning Kamp wrote:

> In message <4980F7D8.8090405 at giraffen.dk>, Anton Stonor writes:
>
>> New try. First, a request with no expire or cache-control header.
>
>>   10 RxProtocol   b HTTP/1.1
>>   10 RxStatus     b 200
>>   10 RxResponse   b OK
>>   10 RxHeader     b Server: Zope/(Zope 2.10.6-final, python 2.4.5,
>> linux2) ZServer/1.1 Plone/3.1.5.1
>>   10 RxHeader     b Date: Thu, 29 Jan 2009 00:10:40 GMT
>>   10 RxHeader     b Content-Length: 4
>>   10 RxHeader     b Content-Type: text/plain; charset=utf-8
>>    9 ObjProtocol  c HTTP/1.1
>>    9 ObjStatus    c 200
>>    9 ObjResponse  c OK
>>    9 ObjHeader    c Server: Zope/(Zope 2.10.6-final, python 2.4.5,
>> linux2) ZServer/1.1 Plone/3.1.5.1
>>    9 ObjHeader    c Date: Thu, 29 Jan 2009 00:10:40 GMT
>>    9 ObjHeader    c Content-Type: text/plain; charset=utf-8
>>   10 BackendReuse b backend_0
>>    9 TTL          c 1495399095 RFC 0 1233187840 0 0 0 0
>
>
> As far as I can tell, a zero TTL (number after "RFC") can only
> happen here if your default_ttl parameter is set to zero, OR
> if there is clock-skew between the varnish machine and the
> backend machine.
>
> Make sure both machines run NTP.
>
> You can test that they agree by running
> 	ntpdate -d $backend
> on the varnish machine (or vice versa).


But would this matter since he is resetting the obj.ttl to 1 day in  
vcl_fetch?

Ric