Welcome! Log In Create A New Profile


1.7 major caching change?

April 03, 2015 06:12PM

Until version 1.6.2 we had a configuration which was working fine to force people to hit the cache:

proxy_set_header Cookie "";
proxy_hide_header Set-Cookie;
proxy_ignore_headers Expires Cache-Control Set-Cookie;
proxy_cache_valid 3m;

and we use a specific proxy_cache_bypass so we BYPASS the cache by ourselves periodically to refresh the cache (under 3m of course).

The thing is, after upgrading to 1.7, it is broken, the bypass still works, but there are some requests not hitting the cache.

03/Apr/2015:21:46:09 +0000 "GET / HTTP/1.1" 200 [...] BYPASS <-- me refreshing the cache
03/Apr/2015:21:47:21 +0000 "GET / HTTP/1.1" 200 [...] EXPIRED <-- random visitor
03/Apr/2015:21:47:29 +0000 "GET / HTTP/1.1" 200 [...] EXPIRED <-- random visitor

Not only it is not hitting the first cached page, but then it should even hit the previous visitor cache because we use proxy_cache_use_stale updating

Are there some new headers we need to ignore in 1.7, or any other major change?

I've looked at the cache folder and i see it creating different files with different filenames/paths but the KEY is the same..

I had tried it with 1.7.9 and we faced the issue so we reverted back to 1.6, i've just tried 1.7.11 and we still have the problem..

Subject Author Posted

1.7 major caching change?

kevinff April 03, 2015 06:12PM

Re: 1.7 major caching change?

kevinff April 03, 2015 06:24PM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 91
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready