How to make proxy revalidate resource at origin

Server NGINX
1

Hi,

I posted this on stackoverflow already but I thought I might have more
luck
here :slight_smile:

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.

Cheers,
Thijs

2

On Sep 27, 2013, at 7:09 PM, Thijs K.
[email protected] wrote:

Hi,

I posted this on stackoverflow already but I thought I might have more luck here
:slight_smile:

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 :slight_smile:

http://trac.nginx.org/nginx/roadmap

3

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?

4

Maybe via Lua?

Posted at Nginx Forum: