Re: Cacheability - changed in Varnish 2?
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: 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 ObjStatusc 200 9 ObjResponse c OK 9 ObjHeaderc Server: Zope/(Zope 2.10.6-final, python 2.4.5, linux2) ZServer/1.1 Plone/3.1.5.1 9 ObjHeaderc Date: Thu, 29 Jan 2009 00:10:40 GMT 9 ObjHeaderc 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). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: [varnish] Re: Cacheability - changed in Varnish 2?
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: 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 ObjStatusc 200 9 ObjResponse c OK 9 ObjHeaderc Server: Zope/(Zope 2.10.6-final, python 2.4.5, linux2) ZServer/1.1 Plone/3.1.5.1 9 ObjHeaderc Date: Thu, 29 Jan 2009 00:10:40 GMT 9 ObjHeaderc 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 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: [varnish] Re: Cacheability - changed in Varnish 2?
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 run. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cacheability - changed in Varnish 2?
Poul-Henning Kamp wrote: 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. Right on! Backend is running on the same box as Varnish for this test. But: you are right about default TTL being 0. After setting default TTL to 60, everything runs smooth. So this issue was not about Varnish versions, but different default TTL configs. Thanks alot. /Anton ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cacheability - changed in Varnish 2?
In message 49817d5c.10...@giraffen.dk, Anton Stonor writes: Poul-Henning Kamp wrote: 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. Right on! Backend is running on the same box as Varnish for this test. But: you are right about default TTL being 0. I hope we don't ship varnish that way on any platforms, the default ttl should be 120 seconds... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cacheability - changed in Varnish 2?
Poul-Henning Kamp wrote: I hope we don't ship varnish that way on any platforms, the default ttl should be 120 seconds... No, the 0 default ttl comes from this one: http://pypi.python.org/pypi/plone.recipe.varnish From the changelog: Add a default_ttl of zero seconds to the Varnish runner to avoid a Varnish bug with the handling of an Expires header with a date in the past. /Anton ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cacheability - changed in Varnish 2?
In message 49818470.10...@giraffen.dk, Anton Stonor writes: Poul-Henning Kamp wrote: I hope we don't ship varnish that way on any platforms, the default ttl should be 120 seconds... No, the 0 default ttl comes from this one: http://pypi.python.org/pypi/plone.recipe.varnish From the changelog: Add a default_ttl of zero seconds to the Varnish runner to avoid a Varnish bug with the handling of an Expires header with a date in the past. That's been fixed, but I can't remember if it made it back to 2.0.x -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
