Refreshing modified content

Jonathan Leibiusky ionathan at
Thu Dec 16 22:33:52 CET 2010

How about using the If-Modified-Since header? If the backend server
interpret this header and answers 304, maybe you could configure
varnish to give back the cached resource. Of course your client should
send that in the request.
Or maybe there is a way to tell varnish to send internally a
conditional request every once in a while?


On 12/16/10, Per Buer <perbu at> wrote:
> Hi,
> On Thu, Dec 16, 2010 at 9:31 PM, Paulo Paracatu
> <paulo at>wrote:
>> If I understood it, the purging method isn't automatic, right? I'd need to
>> purge the content everytime it is modified.
> Hi,
> Nobody purges the cache manually. You get your CMS to purge the cache for
> you.
> This is kinda stupid... I host more than 10k sites, modifying files
>> everytime. If I set a high TTL, the backend will be happy and the
>> webmaster
>> will be angry. If I set a low TTL, the webmaster will be happy, but the
>> backend will die. Plus, there is no point using a cache if the TTL is low.
> It isn't stupid, computers don't have intuition and you have to actually
> tell them when you update data. If you can propose another way of getting
> the cache to magically purge itself of stale content please share it with
> us. :-)
> --
> Per Buer, Varnish Software
> Phone: +47 21 98 92 61 / Mobile: +47 958 39 117 / Skype: per.buer
> Varnish makes websites fly!
> Want to learn more about Varnish?

More information about the varnish-misc mailing list