By default, all files will have a cache lifetime of only 7 days because that's what's set in the .htaccess file. It would be great if we could specify a longer lifetime for static assets.
Here is the recommended code from AdvAgg for Drupal:
<FilesMatch "^(css|js)__[A-Za-z0-9-_]{43}__[A-Za-z0-9-_]{43}__[A-Za-z0-9-_]{43}.(css|js)(\.gz|\.br)?">
# No mod_headers. Apache module headers is not enabled.
<IfModule !mod_headers.c>
# No mod_expires. Apache module expires is not enabled.
<IfModule !mod_expires.c>
# Use ETags.
FileETag MTime Size
</IfModule>
</IfModule>
# Use Expires Directive if apache module expires is enabled.
<IfModule mod_expires.c>
# Do not use ETags.
FileETag None
# Enable expirations.
ExpiresActive On
# Cache all aggregated css/js files for 52 weeks after access (A).
ExpiresDefault A31449600
</IfModule>
# Use Headers Directive if apache module headers is enabled.
<IfModule mod_headers.c>
# Do not use etags for cache validation.
Header unset ETag
<IfModule !mod_expires.c>
# Set a far future Cache-Control header to 52 weeks.
Header set Cache-Control "max-age=31449600, no-transform, public"
</IfModule>
<IfModule mod_expires.c>
Header append Cache-Control "no-transform, public"
</IfModule>
</IfModule>
</FilesMatch>
GitHub Issue #:
3937
Recent comments
Hi, so working through Amilenkov's useful suggestions in turn unpublished? - I can see the page itself when not logged in. I did then edit and added a menu link from the page...
menu partially working
Amilenkov's suggestions are spot on. As for the greyed out Menu module, that's because there must be another module that depends on Menu. Core will gray out modules that cannot be disabled (e.g...
menu partially working
Welcome to the Backdrop community! My first suspicion would be access to the destination page. Backdrop checks access when building the menu, so a link can be enabled but still be hidden...
menu partially working