Refreshing modified content

[Paulo Paracatu]

If I understood it, the purging method isn't automatic, right? I'd need to
purge the content everytime it is modified.
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.

2010/12/16 thebog <thebog at gmail.com>

> ---------- Forwarded message ----------
> From: thebog <thebog at gmail.com>
> Date: Thu, Dec 16, 2010 at 9:22 PM
> Subject: Re: Refreshing modified content
> To: Paulo Paracatu <paulo at aliancaproject.com>
>
>
> The "best" thing to do in this case is to purge the object from the
> cache. (http://www.varnish-cache.org/docs/trunk/tutorial/purging.html)
>
> Or change the URL :)
>
>
> YS
> Anders Berg
>
>
> On Thu, Dec 16, 2010 at 9:09 PM, Paulo Paracatu
> <paulo at aliancaproject.com> wrote:
> > Hi. I'm trying Varnish on my servers, and so far I'm quite happy with it.
> > But I have a little problem: I uploaded an image, hit it in my browser,
> then
> > I modified it and reuploaded it, and tried to hit it again, and the cache
> > serves the old image. It does not serve the new image until the ttl
> (120s)
> > is expired.
> > I tried the "VCLExampleEnableForceRefresh", but the varnish-cache is only
> > refreshed with ctrl-f5/no-cache header. Is this the normal behavior of
> > varnish, or is it possible to 'revalidate' the cached content with the
> > backend?
> > PS: My browser's cache is disabled.
> > Thanks
> > _______________________________________________
> > varnish-misc mailing list
> > varnish-misc at varnish-cache.org
> > http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
> >
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20101216/0abb2f66/attachment-0003.html>