Search results

The simplest way to find out if cache plugin is responsible for this issue is to check the cache header. Do you know how to check it?

What happens if you enter /it/contattaci.html or /en/contact-us.html into the input for excluding URLs to be cached? This should work, but there is still a hard core method to prevent URLs from being cached.

Yes. ;) https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

A bit more information please.

Nothing at all. I'm trying to find the answer to why the cache is purged by simply changing the UA.

@AndreyPopov I have updated the extension and now I also get this cookie. With this extension I tried to reproduce the phenomenon purging the cache with FF simulated view function and surprise the cache is not purged. The question now is if this only happens with your custom code? Where I can...

Now I know why I can't find any code about this cookie. I've donwloaded extension from LiteSpeed website and not from github....

This doesn't answer my question or I don't understand your answer. Is this cookie custom set by your code?

@AndreyPopov Where does this cookie come from? Is it generated by cache extension or by your custom code? _lscache_vary: browser%3Asafari%2Cdevice%3Atablet

Could you post the(se) URLs, without domain name?

A scraped copy of https://www.litespeedtech.com/docs/webserver/config/tuning/#maxDynRespSize Don't know the details, but I know that providing sources for Download with such big size often fails due to the nature TCP. There is a high risk that packets are lost while download. @ZorzStudios...

Because Max Dynamic Response Body Size is a system immanent issue with LSWS/OLS. The question is not about how to store such large files, it is about to download it.

OS and file system doesn' matter in this case if he use LiteSpeed web server (LSWS or OLS). It's a question of limits that are defined in configuration, but download of such huge files often fails, so @ZorzStudios should think about alternate download method other than http.

I've just purged cache of the homepage.

@AndreyPopov I can't remember if I told you that I can purge the cache of your page.... So you are also affected from this crazy issue.

Do you have access to Web Admin Console of LiteSpeed web server?

The crazy thing is that only the cache of a requested URL is purged if you change the simulated view in browser and not the entire cache. LSWS or LScache doesn't care of the browser. It only checks headers and the UA, although UA is a header.

This is what has to be found out.

Chrome browser doesn't have a good simulated view function as FF, so it can only be provoked with FF, but will try it with curl tomorrow.

Yes. It is only to simulate. It doesn't matter how much users of your page use FF. This issue is regardless which browser is used if the server purges the cache.