How to make proxy revalidate resource at origin

[Thijs Koerselman]

Aha, I'm hoping that will include If-None-Match, since I'm using etags
instead of last modified dates.

Is there maybe a 3rd party module that supports this already?


On Fri, Sep 27, 2013 at 5:14 PM, Andrew Alexeev <andrew at nginx.com> wrote:

> On Sep 27, 2013, at 7:09 PM, Thijs Koerselman <thijskoerselman at gmail.com>
> wrote:
>
> > Hi,
> >
> > I posted this on stackoverflow already but I thought I might have more
> luck here :)
> >
> >
> http://stackoverflow.com/questions/19023777/how-to-make-proxy-revalidate-resource-from-origin
> >
> > In short, I can't find a way to make nginx revalidate a cached resource
> with the origin. Whenever nginx is in front of my server, the origine never
> returns a 304. Nginx just gets a new copy whenever it expires, and I can't
> trigger a revalidate either. I've tried different approaches with
> cache-control headers but nginx doesn't seem to respect them.
>
> You may want to check this :)
>
> http://trac.nginx.org/nginx/roadmap
>
> > Cheers,
> > Thijs
> > _______________________________________________
> > nginx mailing list
> > nginx at nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130927/fb0e273e/attachment.html>