Thread Starter
masvil
(@masvil)
I figured out. It happened because I migrated the site to an OpenLiteSpeed server, so .htaccess cache headers were ignored. I fixed by adding some cache rules on Cloudflare in addition to the one generated by Super Page Cache.
Dev, before we close this ticket, is there another way to fix this issue?
Plugin Support
Kush
(@kushnamdev)
Hi @masvil,
We haven’t received similar reports from other users, but I will investigate this further and get back to you. In the meantime, could you please share the rules you’ve added on Cloudflare? This information could be helpful for other users in the community who may encounter a similar situation.
Best regards,
Thread Starter
masvil
(@masvil)
If you haven’t received similar reports from other users, it’s because no one tried to use your plugin on a OLS (OpenLiteSpeed) web server, or they just aren’t aware of the missing cache headers. LiteSpeed devs explain the differences between LSWS (LiteSpeed Enterprise Web Server, commonly called “LiteSpeed”) and OLS (Open LiteSpeed) here: https://blog.litespeedtech.com/2023/01/16/openlitespeed-or-litespeed-enterprise/, specifically in the “.htaccess” section.
OLS (OpenLiteSpeed) web servers are mostly shipped by modern VPS control panels because they don’t need to buy a license.
The “Browser TTL” cache rules to add on Cloudflare in case of OLS are to reproduce the ones added by the plugin to the .htaccess file, which are ignored. I see you have a note for NGINX users, but it doesn’t work on OLS.
-
This reply was modified 1 year, 1 month ago by
masvil.
Plugin Support
Kush
(@kushnamdev)
Hi @jsor,
Thanks for pointing this out.
The plugin aims to optimize cache behavior for full pages, but handling cache headers for static assets like JS and CSS files often depends on the server configuration or any additional CDN layer in use. While we don’t directly control static asset headers, we recommend reviewing your server or CDN settings to ensure optimal caching for these file types.
We appreciate your feedback and hope this helps clarify the current behavior.
Best regards,
