Browser caching – IMHO you are wrong

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://www.ads-software.com/support/topic/expiresdefault-error-message-remove-from-htaccess-file/) but the thread didn’t rise import issues that need to be risen.

1. From what I understand, LSC does only page caching, that is why I’m 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 shoulnd’t 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.

<FilesMatch “\.(woff|woff2|ttf|svg|otf|eot)$”>
ExpiresDefault A691200
</FilesMatch>

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 there’s a script that doesn’t use the ExpiresDefault but does the same. So what is the point in suggesting one over the other?

4. In my view, your plugin shouldn’t 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 shouldn’t 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 P?aneta