Clarification on x-litespeed-cache: miss showing inconsistently across pages

  • Resolved cocoa1

    (@cocoa1)


    11 months, 1 week ago

    Hi team,

    I’m using the Super Page Cache for Cloudflare plugin and would like to confirm if the following behavior is expected.

    My Setup:

    • Web server: LiteSpeed
    • LiteSpeed Cache plugin: Active, but page cache is disabled (only using it for QUIC.cloud CSS/JS optimization)
    • Page caching: Fully handled by Super Page Cache for Cloudflare
    • Cloudflare: Active and proxied

    🧪 What I’m Observing:

    1. On some pages (like About, Contact, etc.), I see: x-litespeed-cache: miss x-wp-spc-disk-cache: HIT
    2. On other pages, like the Privacy Policy, I see: x-wp-spc-disk-cache: HIT But no x-litespeed-cache header at all.
    3. On the homepage only, I still see: x-litespeed-cache: miss x-wp-spc-disk-cache: HIT

    ❓ My Questions:

    • Is it normal for the x-litespeed-cache header to be missing on some pages if they’re served directly from SPC disk cache or Cloudflare edge?
    • And more specifically:
      Why is the x-litespeed-cache: miss header still showing only for the homepage, even though LiteSpeed page cache is disabled and SPC is supposed to handle all page caching?

    From my understanding, if SPC (or Cloudflare) serves the page before it hits the origin, then LiteSpeed’s headers may be skipped — but I just want to confirm this behavior is expected, especially the case with the homepage.

    Thanks in advance for your help and for maintaining this awesome plugin!

    Best regards,
    cocoa1

    EDIT:

    I just checked and I see other pages with x-litespeed-cache: miss. Is this because, when the cache is cleared and a new page is opened, the page is created with php request directly from server?

    and when the page is ready and is cached with super page cache with CF, it doesn’t show the x-litespeed-cache: miss after that?

    • This topic was modified 11 months, 1 week ago by cocoa1.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kush

    (@kushnamdev)

    10 months, 4 weeks ago

    Hi @cocoa1,

    Thanks for outlining your setup and observations in such detail.

    Here’s the lowdown:

    1. Missing x-litespeed-cache headers When Super Page Cache serves a page from its disk cache or via Cloudflare, the request often never reaches your origin, where LiteSpeed’s page cache would normally add its headers. That’s why you see x-wp-spc-disk-cache: HIT but no LiteSpeed header, it’s expected behavior.
    2. Why the homepage still shows x-litespeed-cache: miss Some themes or plugins bypass the static cache on the homepage on first load, triggering a PHP request. That generates the miss header. After that first request, Super Page Cache stores the page, the next visit should pick it up from disk or edge cache, and the LiteSpeed header disappears.

    In short, seeing x-litespeed-cache: miss initially but not on subsequent visits is normal especially on fresh cache clears or first visits to uncached pages.

    Hope that clears things up!

    Best regards,

    Thread Starter cocoa1

    (@cocoa1)

    10 months, 4 weeks ago

    Thank you so much. I actually tried it after clearing the cache, so that explains it.

    This plugin is great. However, please disable the instant.page js file being loaded when the option is turned off completely in the next update.

    I am using Perfmatters speculative load with prerender enabled so it interferes with that setting.

    • This reply was modified 10 months, 4 weeks ago by cocoa1.
    Thread Starter cocoa1

    (@cocoa1)

    10 months, 3 weeks ago

    I have checked it again and this time these headers are showing at the same time even after loading page from different browsers, in incgnito mode.

    cf-cache-status: HIT

    x-dns-prefetch-control: on

    x-litespeed-cache: hit

    x-wp-cf-super-cache-active: 1

    x-wp-cf-super-cache-cache-control : s-maxage=31536000, max-age=60

    x-wp-spc-disk-cache: HIT

    Can you tell me what’s going on here exactly?

    I have these settings enabled in LS cache html setting

    DNS Prefetch Control

    Remove Query Strings

    HTML Minify

    Is this because Litespeed page cache is still being turned on or being used and interfering with the Super page cache?

    • This reply was modified 10 months, 3 weeks ago by cocoa1.
Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Clarification on x-litespeed-cache: miss showing inconsistently across pages’ is closed to new replies.