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

Hello! On Wed, Jul 16, 2014 at 02:14:54AM -0400, quoter wrote: > 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

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

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 d

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

It is good to have `$request_method` in the cache key since HEAD and GET methods may share same hash for content they point to Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239689,243239#msg-243239 ___ nginx mailing list nginx@nginx.org http

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

Default approach doesn't work for me. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239689,243238#msg-243238 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

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

Hello! On Thu, May 30, 2013 at 06:41:50AM -0400, kapouer wrote: > Hi, > i struggled a little to get nginx to cache 304 responses from backend using > proxy_cache. > What happens when configuring proxy_cache is that 304 responses are not > happening because > nginx strips If-None-Match request hea

if-none-match with proxy_cache : properly set headers

Hi, i struggled a little to get nginx to cache 304 responses from backend using proxy_cache. What happens when configuring proxy_cache is that 304 responses are not happening because nginx strips If-None-Match request headers. It is a workaround to prevent the client from getting an empty response