[try_files_is_evil_too] try_files without open_file_cache
What this check looks for
This plugin warns when try_files is used but open_file_cache is not configured or is off.
Why this is a problem
try_files checks each candidate file with a stat() call: one extra system call when the first candidate exists, plus one for every candidate a request skips. Without open_file_cache, every request repeats them. Each call is cheap, so this matters mostly on busy servers.
Bad configuration
location / {
try_files $uri $uri/ /index.html;
}
Better configuration
Enable open_file_cache to cache file metadata:
open_file_cache max=10000 inactive=30s;
open_file_cache_valid 60s;
open_file_cache_min_uses 2;
open_file_cache_errors on;
server {
location / {
try_files $uri $uri/ /index.html;
}
}
Additional notes
open_file_cache_errors on;, as in the example above, also caches failed lookups, so a file created after a miss is not found until open_file_cache_valid (60 seconds by default) has passed.
Caching may not suit file trees that change constantly, or filesystems where metadata caching is risky.