Nginx cache Expiration Management Summary

Nginx cache Expiration Management Summary Let's look at a classic configuration: proxy_cache_path/cachelevels1: 2keys_zonecache_pool: 512minactive1mmax_size10g; location ~. *\. (Jpg | gif | png) $ {proxy_next_upstreamhttp_50... nginx cache Expiration Management Summary Let's look at a classic configuration: proxy_cache_path/cache levels = keys_zone = cache_pool: 512 minactive = 1 m max_size = 10g; location ~. *\. (Jpg | gif | png) $ {response http_502 http_504 error timeout invalid_header; proxy_cache cache_pool; response 200 304 2 m; response $ host $ uri $ is_args $ args; proxy_set_header Host $ host; proxy_set_header X-Forwarded-For $ remote_addr; proxy_pass http://storage1 ; Expires 10 m;} someone on the forum asked me what they meant by the three times and what they used? First read the explanation on the official website: Cached data that are not accessed during the time specified by the inactive parameter get removed from the cache regardless of their freshness. by default, inactive is set to 10 minutes. (If the cached data is not accessed within the time specified by the inactive parameter, it will be removed from the cache, whether or not it is just generated. The default value of inactive is 10 minutes.) Sets caching time for different response codes. for example, the following directivesproxy_cache_valid 200 302 10 m; proxy_cache_valid 404 1 m; set 10 minutes of caching for responses with codes 200 and 302, and 1 minute for responses with code 404. expires: Controls whether the response shoshould be marked with an expiry time, and if so, what time that is. here, the inactive time indicates the specified time of a file. Is removed from the storage system, regardless of the time you set in proxy_cache_valid. Proxy_cache_valid ensures the maximum available time when it is accessed within the inactive period. Proxy_cache_valid defines an absolute Expiration Time (the first cache time + the configured cache time). at this point, the object is considered to have expired and then the data is retrieved from the backend, although it is frequently accessed (the so-called inactive time ). Expires is not in this expiration control system. it is used in the response sent to the client to add the "Expires" header.