Re: proxy_cache_background_update after cache expiry

2017-04-06 Thread IgorR
thank you Maxim, the resourse was saved to cache but was quickly expiring in the browser causing a Cache-Control: no-cache header to be sent. Sending something like Cache-Control: public,max-age=15,s-maxage=240;must-revalidate,stale-while-revalidate=240 together with Last-Modified/ETag from t

Re: proxy_cache_background_update after cache expiry

2017-04-05 Thread Maxim Dounin
Hello! On Wed, Apr 05, 2017 at 07:32:01AM -0400, IgorR wrote: > Hello, > > I'm trying to configure nginx to use proxy_cache_background_update but it > seems like after expiry it still waits for the full roundtrip to the > backend, returning a MISS in X-Cache-Status. What am I MISSing? > > I'm u

Re: proxy_cache_background_update after cache expiry

2017-04-05 Thread Jean-Paul Hemelaar
Hi, I have a similar issue: http://mailman.nginx.org/pipermail/nginx/2017-March/053198.html I noticed (using tcpdump) that all data except the last package is send immediately. Can you verify it that's happening in your case as well? JP On Wed, Apr 5, 2017 at 1:32 PM, IgorR wrote: > Hello, >

proxy_cache_background_update after cache expiry

2017-04-05 Thread IgorR
Hello, I'm trying to configure nginx to use proxy_cache_background_update but it seems like after expiry it still waits for the full roundtrip to the backend, returning a MISS in X-Cache-Status. What am I MISSing? I'm using nginx 1.11.12 under ubuntu 14.04 running inside docker, but hopefully thi