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

2009-01-29 Thread Ricardo Newbery
On Jan 29, 2009, at 12:34 AM, Poul-Henning Kamp wrote: In message 4980f7d8.8090...@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:

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

2009-01-29 Thread Poul-Henning Kamp
In message 9e3c9108-eb3a-485c-adc0-948860f4b...@digitalmarbles.com, Ricardo N ewbery writes: 9 TTL c 1495399095 RFC 0 1233187840 0 0 0 0 But would this matter since he is resetting the obj.ttl to 1 day in vcl_fetch? Yes, the RFC2616 based TTL is calculated before vcl_fetch is

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

2009-01-28 Thread Ricardo Newbery
On Jan 28, 2009, at 2:23 AM, Anton Stonor wrote: sub vcl_recv { set req.grace = 120s; set req.backend = backend_0; } Is this truly all you have in vcl_recv? This will mean that any cookied requests will get passed. Is this intentional? Ric

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

2009-01-28 Thread Anton Stonor
Ricardo Newbery skrev: sub vcl_recv { set req.grace = 120s; set req.backend = backend_0; } Is this truly all you have in vcl_recv? This will mean that any cookied requests will get passed. Is this intentional? No, this is not a production setup. My problem is not that I cache

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

2009-01-28 Thread Ricardo Newbery
On Jan 28, 2009, at 4:29 PM, Anton Stonor wrote: Ricardo Newbery skrev: sub vcl_recv { set req.grace = 120s; set req.backend = backend_0; } Is this truly all you have in vcl_recv? This will mean that any cookied requests will get passed. Is this intentional? No, this is