Reverse proxy caching for dynamic content

Patrick 201904-nginx at
Wed May 15 08:42:08 UTC 2019

On 2019-05-15 03:57, flierps wrote:
> I want to cache dynamic content, so every request needs to be revalidated.
> This way when I get multiple fresh GET requests for an expensive resource,
> Nginx can revalidate with the backend that only needs to generate a 304's
> and the full content can be served to the clients.

As you note, If-Modified-Since has a smallest time resolution of 1 second.

Can the upstream publish ETags and handle If-None-Match request headers
so that nginx can get 304s in response?


More information about the nginx mailing list