How to increase Nginx FastCGI cache expiration?

marowi

Dear Enhancers,

can anyone tell me if it is possible to change the Nginx FastCGI cache expiration for a website? By default, it expires every 60 minutes. For a mostly static website, I would like to increase this to 12 hours.

Best regards
Manuel

rdbf

By writing a script that changes the .conf files and monitors them for changes when Enhance auto-generates them again.

Perhaps something is possible on the overrides, but you'll quickly run into conflicts that will simply kill nginx for that server until the errors are resolved.

nhybgtvfr

it's set on the 1st line of the vhost config...
fastcgi_cache_path /var/nginx_cache/<domain.tld> levels=1:2 keys_zone=<domain.tld>:100m inactive=60m;

you could try using an override, but i believe the system will throw a fit if the cache is specified more than once in the vhost config and nginx will be down for everyone

alternatively, you could just edit the config file, set a long inactive period, and then make the file immutable, but then the system can't make any updates to the vhost config, and i have no idea how it will react to failing to make a change.

rdbf

nhybgtvfr it's set on the 1st line of the vhost config...

It's also in the location ~ \.php$ { block:

fastcgi_cache_valid 60m;

nhybgtvfr but then the system can't make any updates to the vhost config

The system doesn't update it, it just overwrites it with a new one based on stored settings.

nhybgtvfr

the part in the php block is separate, that provides a default value for the cache lifetime of an object if any of
X-Accel-Expires/Expires/Cache-Control are not specified for it.

fastcgi_cache_path ... inactive= is used to define how long objects should be kept in the cache without access from a browser.

with fastcgi_cache_valid 30m and fastcgi_cache_path ... inactive=60m all replies from the server without any Cache-control headers will be valid for 30 minutes, but can still be used after 30 minutes if there are problems with the server if fastcgi_cache_use_stale is configured.
But the cached object will be removed from the cache if there has been no request for that object from users for 60 minutes.

and if the vhost config file is made immutable, the system cannot overwrite it with a new one, regardless of any stored settings. i'm not sure how the system will react to the failure to overwrite the existing file.