![]() ![]() NGINX first writes files that are destined for the cache to a temporary storage area, and the use_temp_path=off directive instructs NGINX to write them to the same directories where they will be cached.When expired content is accessed, NGINX refreshes it from the origin server and resets the inactive timer. Expired (stale) content is deleted only when it has not been accessed for the time specified by inactive. NGINX does not automatically delete content that has expired as defined by a cache control header ( Cache-Control:max-age=120 for example). Inactive content differs from expired content. In this example, a file that has not been requested for 60 minutes is automatically deleted from the cache by the cache manager process, regardless of whether or not it has expired. inactive specifies how long an item can remain in the cache without being accessed. ![]() When the cache size reaches the limit, a process called the cache manager removes the files that were least recently used to bring the cache size back under the limit. It is optional not specifying a value allows the cache to grow to use all available disk space.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |