Hi @pmattei
I hope you’re well today!
Browser caching is controlled by HTTP headers sent by webserver and Hummingbird can only attempt to control those headers – in case of Apache it’s via .htaccess file.
What you described suggests that it may be not possible to write to .htaccess currently.
I’d suggest checking if .htaccess is writable first. By accessing site files via FTP (or cPanel’s “File Manager” or similar way) you should see what are the “permissions” for that file and if they are like 555, 554, 544 or 444 it would man file is not writable.
If it’s 775 – it should be writable. If it’s 755 it may or may not be writable depending on the server configuration.
If that’s not the case, then it may also be possible that the site is either not powered by Apache (and the server is incorrectly detected) or it is a hybrid setup e.g. Nginx + Apache. In such case rules are probably added to .htaccess already but they are overwritten by server-wide settings of Nginx webserver. In such case you would need to contact your host for help with changing Browser Cache settings.
Also, are you by any chance using CloudFlare on site? If so, the first step should be to connect CloudFlare to Hummingbird, as described here
https://wpmudev.com/docs/wpmu-dev-plugins/hummingbird/#cloudflare-integration
because CloudFlare would also override .htaccess browser caching configuration.
Kind regards,
Adam
Thank you for the quick response! It looks like our htaccess is not writable, so that is likely causing it. Will work on getting that updated and will try again, so this should be closed for now.
Thanks again.