Therefore, APO might use BYPASS or you set it to, then Page Rule Caches Everything, then LSCache has got some “html” cached version and serves this … Nevertheless, issues like other visitors, like non-logged-in users would end-up having and seeing the “admin top bar” from the served and cached version of the “logged-in” admin user when visting your homepage or some other webpage → not good. That’s even challenging for an advanced and experience user to manage. May I ask, how do you expect it to work all together and purge/flush the cache each time “when you want? or automatically?” on all 3 different platforms?
Cloudflare Page Rule with Cache Everything.LSCache plugin for WordPress (which should work fine for 1.Litespeed cache at the origin host/server.So, you are trying to combine 3 different “caching systems” to work perfectly, as far as I understand? I will post the same question at Litespeed forums, to see what I can get from there as well. I could even be confused and thinking or trying the wrong things - so I would appreciate any suggestion that would take me into the right direction. So, I was hoping if I could get any helpful tips or other ideas, or suggestions for a proper configuration for the two technologies. I recently disabled the Cache Everything on CF and have purged all caches - but still getting pages with the issue. So, I might be getting the issue with Chrome but not with Firefox and/or a customer might be getting the issue, while I am not. Since the problem occurs in some pages and only after some days and I need to keep searching the pages in order to spot if this has occurred, it makes it hard to tell what effects can specific configurations have - so overall it’s hard to re-produce, to debug and diagnose and reach to a solution.Īnother thing to note is that the issue may not be occurring with all the browsers and maybe not all the users will encounter it (speaking for the same pages at the same time). I have to go and Purge Cloudflare’s cache, in order to get a fresh copy of the pages’ content and links to their assets. I have tried various different configurations but despite all my efforts, I am still experiencing similar issues. This causes problems in using the front of the pages, since functionality is broken. This is only a problem with combined, minified JS files so far, and not with any CSS files. It seems that somehow the Litespeed Cache has purge them and generated new ones with a new URL, but Cloudflare still serves the old ones. Now the issue that I am facing is that from time to time, on certain pages, their assets files remain cached on Cloudflare, therefore the visitors browsers load those files, while that have expired and are non existent on my website/server anymore - returning a 404 error. Page Rules: Cache Level: Cache Everything for the front-end pages - But recently disabled that rule.Īutomatic Platform Optimization for WordPress: On + Cache By Device Type On the Cloudflare side I have enabled the following:īrowser Cache TTL: Recently changed it to: Respect Existing Headers I am compressing and combining files on the WP site with the LSCache plugin and also have LSCache enabled (or disabled in order to troubleshoot).
Lscache on litespeed web server. pro#
I am using Litespeed LSCache plugin - not with quic.cloud - on Litespeed server and also a Cloudflare pro plan. I am after ideas and tips to help solve the following issue.
0 kommentar(er)
