Wordpress LScache Plugin: Browser caching ? IMHO you are wrong
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, After the last update LSC displayed an error about browser caching set with the ExpiresDefault rules. I have read the post about it here (https://wordpress.org/support/topic/expiresdefault-error-message-remove-from-htaccess-file/) but the thread didnt rise import issues that need to be risen. 1. From what I understand, LSC does only page caching, that is why Im wondering why it messes with browser caching. In my view if a system admin installs a browser caching plugin (like hummingbird for example) or adds htaccess rules to do the same, than they should be aware of what they are doing and be RESPONSIBLE for that. In my view, your plugin walks on their territory making demands but not offering anything in exchange. 2. In the thread mentioned above you say that ExpiresDefault shoulndt be used since in caches HTML. However, it can (and I think in most cases is) used within conditions like the one below which targets only font files. ExpiresDefault A691200 That is why in most cases LSC shows ExpiresDefault error to everyone, even to the majority of people who have it configured correctly. 3. In that thread I mentioned before theres a script that doesnt use the ExpiresDefault but does the same. So what is the point in suggesting one over the other? 4. In my view, your plugin shouldnt consider every script using ExpiresDefault as incorrect and throw an error. Rather than that it should check whether the expires default is used on HTML since it is the only rule that shouldnt be used. Alternatively it should show a notice saying that caching HTML by ExpiresDdefault is a bad idea. 4. I really believe that if your plugins shows an error like this (or even a notice suggested above) than it should offer an alternative, e.g. by suggesting replacing those rules with the ones that you are 100% sure are correct. Have a nice day, Krzysztof Planeta Hi @chrisplaneta, Really appreciated for your suggestion. We will update this part of logic in this weeks release. Should be v1.1.4.1. Thanks a lot, Hai Good points indeed. Thanks Krzysztof. After thorough discussion, we this maybe its better to remove that check in code for now. Thanks for your feedback.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference