Wordpress LScache Plugin: Public Cache
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, My header is showing the cache as private. Is there a way to set the cache as public? Currently ESI is not live. You should not see the cache header as private. Can you give a link and also your webadmin server->cache check policy screenshot? Hi, Here is my site https://www.celebrityhealthcritic.com/ I dont have access to webadmin, but i can tell my host to check this if you tell me what to check for. Currently, using chrome developer tools and looking at network, when i view the header for http://www.celebrityhealthcritic.com i can see the header x-litespeed-cache:miss. The miss seems to happen frequently when cache is private, but when i disable the plugin and enable litespeed using htaccess, as below, it doesnt show private in the header and the page remains cached. Also, im not seeing the litespeed cache control headers either. This doesnt show private in the header CacheEnable public RewriteEngine On RewriteCond % REQUEST_METHOD ^GET|HEAD$ RewriteCond % REQUEST_URI !login|admin|register|post|cron RewriteCond % QUERY_STRING !nocache RewriteRule . ? [E=Cache-Control:max-age=2592000] im seeing the cache control and tag headers only when cache is a miss, they dont show when cache is hit. Not sure if thats how its meant to be? The rewrite rule based cache is deprecated. The pages keep missing which is not correct. Not sure if you configured correctly. Can you create a tix and give the access to your wp-admin? Hi, I figured out what was happening. I had my htaccess open while i was editing it during activation of the plugin. This seemed to have stopped the plugin entering anything in the htaccess. I closed the htaccess, deactivated plugin and reenabled it. Cache is now showing hit and i dont see the private anymore. Not sure why the private isnt showing now as it was before, but it might be because i sent email to host telling them to check if ESI is active as per your previous comment. Will wait to hear back from them to see if thats the case. An issue im still having is that the Default Front Page TTL is the same as the Default Public Cache TTL despite setting different values for these in the plugin. I would like my posts to have a different expiry time from the homepage as the posts change infrequently but the homepage changes frequently. Does this actually matter anyway? Because if the homepage is updated wouldnt the cache get regenerated anyway? Thanks for letting us know. You dont have to get them check ESI part as in our plugin ESI is not activated/live yet. The private issue you met may come from your hardcoded rule. The Default Public Cache TTL and Default Front Page TTL both work well. Cant find more details about your issue. Homepage is regenerated based on the setting in your Purge Rules setting. ok, i wasnt using the hardcoded rule and the plugin at the same time. So not sure whats happening then. Should i be seeing the litespeed cache and tag headers when it shows a hit? As these only seem to show when there is a miss. Ive also noticed when using this plugin the last modified header is not sent. Is this not supported? You may or may not see the tags headers. If you turn on debug, you will see them in the end of source code. Last modified header isnt supported yet. Do you think it should be added? According to this site https://varvy.com/ifmodified.html the last modified header is in the google guidelines. So yes, i think it should be added, plus it also helps to reduce server load by not having to download content that hasnt changed.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference