LiteSpeed Cache for XF2 - Community

LiteSpeed Cache for XF2 - Community 2.3.0

No permission to download
Overview FAQ Updates (10) Reviews (13) History Discussion
After testing LSCache on XF, it’s clear that full page caching is not compatible with dynamic forum architecture. When LSCache is enabled, several recurring issues appear:
  • login loops and session validation errors,
  • new posts/edits appearing late for guests,
  • cookie vary conflicts with XenForo’s session handling,
  • LSCache and the PWA service worker claiming the same HTML output,
  • occasional delivery of guest cache to logged-in users.
Our stable setup is: Cloudflare (static CDN), Redis object cache, OPcache. Fully compatible with XenForo’s dynamic nature. All inconsistencies disappear the moment LSCache is disabled. Until the LiteSpeed team provides XF-specific invalidation/compatibility support, LSCache is not a reliable solution for forum-based platforms.
 
I was gonna ask the team to put an "Unmaintained" tag on this add-on but looks like it has already been.
 
Ricsca said:
When you make certain statements, you have to provide numbers.
Can you give me statistics on people who have abandoned a site because they couldn't find a black theme?
I bet you don't have them because they don't exist! There isn't a single sane person who, if they can't find a black theme, leaves and doesn't visit the site... let's be serious... Then if we want to invent fake problems, that's another matter...
Click to expand...
Having to change the entire color theme of a site is ridiculous. Of course if you entirely change a site you might lose members.
 
Tamer said:
After testing LSCache on XF, it’s clear that full page caching is not compatible with dynamic forum architecture. When LSCache is enabled, several recurring issues appear:
  • login loops and session validation errors,
  • new posts/edits appearing late for guests,
  • cookie vary conflicts with XenForo’s session handling,
  • LSCache and the PWA service worker claiming the same HTML output,
  • occasional delivery of guest cache to logged-in users.
Our stable setup is: Cloudflare (static CDN), Redis object cache, OPcache. Fully compatible with XenForo’s dynamic nature. All inconsistencies disappear the moment LSCache is disabled. Until the LiteSpeed team provides XF-specific invalidation/compatibility support, LSCache is not a reliable solution for forum-based platforms.
Click to expand...
Did this happen recently because my 2 xenforo websites running litepseed slowed down a couple weeks ago.
 
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
What’s added compared to the stock version
  • ACP-based cache and .htaccess management
  • day/night support
  • separate desktop/mobile cache
  • crawler warms both cache variants
  • purge by URL, tags, and entities
  • targeted warmup after purge
  • logs and diagnostics in the admin panel
Why tags matter — they allow related cache to be purged precisely without using purge all

How day/night works — separate vary handling prevents light and dark versions from being mixed in cache

How the crawler works — each URL is warmed in 2 passes: desktop + mobile
Code: 
34.116.*.* - - [11/Mar/2026:13:17:28 +0000] "GET /tags/om642/ HTTP/1.1" 200 14882 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
34.116.*.* - - [11/Mar/2026:13:17:28 +0000] "GET /tags/om642/ HTTP/1.1" 200 14880 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Mobile/15E148 Safari/604.1"
 
Line said:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
What’s added compared to the stock version
  • ACP-based cache and .htaccess management
  • day/night support
  • separate desktop/mobile cache
  • crawler warms both cache variants
  • purge by URL, tags, and entities
  • targeted warmup after purge
  • logs and diagnostics in the admin panel
Why tags matter — they allow related cache to be purged precisely without using purge all

How day/night works — separate vary handling prevents light and dark versions from being mixed in cache

How the crawler works — each URL is warmed in 2 passes: desktop + mobile
Code: 
34.116.*.* - - [11/Mar/2026:13:17:28 +0000] "GET /tags/om642/ HTTP/1.1" 200 14882 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"
34.116.*.* - - [11/Mar/2026:13:17:28 +0000] "GET /tags/om642/ HTTP/1.1" 200 14880 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Mobile/15E148 Safari/604.1"
Click to expand...
Thank you for your interest in our cache. This looks cool :cool:

The only thing I would mention is to make sure that you make it clear that your add-on is not directly affiliated with LiteSpeed Technologies so there is no confusion. Otherwise, assuming it works as advertised, great job.

Regards,
-Michael A.
 
You must log in or register to reply here.
Back
Top Bottom