Two caching layers working together.
THE ARRANGEMENT
LiteSpeed cache on our servers generates and stores the page. Cloudflare caches static assets and, if configured, the page itself.
WHY BOTH
Server-side caching means we do not run your application for every request. Cloudflare means many requests do not reach us at all.
Together they cover different parts of the problem.
THE ORDER OF SETUP
Server-side caching first. It delivers most of the benefit and understands your application's exclusions.
Then Cloudflare.
THE COMPLICATION
Two caches means two places to purge. A change that does not appear may be held in either.
Some caching plugins can purge Cloudflare automatically when they purge themselves. Configure that if available; it removes a recurring confusion.
WHAT NOT TO DO
Enable minification in both. Choose one.
Cache HTML at Cloudflare without matching exclusions to your server-side rules.
TROUBLESHOOTING ORDER
Application cache, then Cloudflare, then browser. Always that order.
