Welcome! Log In Create A New Profile

Advanced

Re: if-none-match with proxy_cache : properly set headers

July 16, 2014 02:14AM
Maxim Dounin Wrote:
-------------------------------------------------------
> Normally you shouldn't cache 304 responses from a backend, but
> rather cache 200 responses from a backend and let nginx to return
> 304 by its own. This is how it works by default.
>
> Do you have problems with the default aproach?
>
> --
> Maxim Dounin
> http://nginx.org/en/donation.html
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Yes I do have some problems with this approach. In our nginx config we use also option "fastcgi_cache_min_uses 5". So response body appears in cache only after 5 user requests. But for our production purposes it is extremely important to return 304 if client response has valid If-None-Match.

---
Dmitry Sukhov
quoter@yandex-team.ru
Subject Author Posted

if-none-match with proxy_cache : properly set headers

kapouer May 30, 2013 06:41AM

Re: if-none-match with proxy_cache : properly set headers

Maxim Dounin May 30, 2013 07:22AM

Re: if-none-match with proxy_cache : properly set headers

neoascetic September 29, 2013 01:19AM

Re: if-none-match with proxy_cache : properly set headers

quoter July 16, 2014 02:14AM

Re: if-none-match with proxy_cache : properly set headers

Maxim Dounin July 16, 2014 09:40AM

Re: if-none-match with proxy_cache : properly set headers

neoascetic September 29, 2013 01:47AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 314
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready