no-store, no-cache, must-revalidate headers

  • Resolved cyrix2000

    (@cyrix2000)


    1 year, 1 month ago

    Somehow Litespeed cache stopped caching pages. I got aware about it because the WordPress health screen complained that there isn’t an active cache plugin anymore.

    Checking the header files of the website, I’m now getting only “Cache-Control: no-store, no-cache, must-revalidate”

    What could be the reason for this?

    Report ID: DSYQLLDC

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support qtwrk

    (@qtwrk)

    which page is that ?

    and this cache-control: no-store, no-cache, must-revalidate is normal and is expected , it has nothing to do with server-side cache

    Thread Starter cyrix2000

    (@cyrix2000)

    The ppage is https://www.onetwo3d.co.uk

    Plugin Support qtwrk

    (@qtwrk)

    it does give cache hit header on me , what are the headers you see ?

    Thread Starter cyrix2000

    (@cyrix2000)

    That’s the error message WordPress is showing:

    “Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status, x-litespeed-cache, x-lsadc-cache, x-qc-cache.

    •  Median server response time was 658 milliseconds. It should be less than the recommended 600 milliseconds threshold.
    •  No client caching response headers were detected.
    • ?A page cache plugin was not detected.”
    Plugin Support qtwrk

    (@qtwrk)

    well , I can assure you there is a x-litespeed-cache header showing up , I don’t know why health tool didn’t detect it

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘no-store, no-cache, must-revalidate headers’ is closed to new replies.