Inconsistent Caching in LiteSpeed Cache: Has Anyone Experienced This?

  • Resolved GinaV

    (@ginavicente)


    3 months, 1 week ago

    Hello everyone,

    I can’t get LiteSpeed Cache to serve cached content for all my pages.

    After setting up the LiteSpeed Cache crawlers, they run normally, but in the “Sitemap List” section, I see the crawler status for each URL in green, indicating a 201 response code. I understand that a 201 Created code indicates that a new resource has been created as a result of the request, and this resource is generally not directly cached. However, the response could contain information about the created resource, and if that resource is accessed later with a GET request, then the response for that new request could be cached.

    When I load any URL on the website for the first time, I see Status Code: 200 OK and x-litespeed-cache: miss.

    When I reload that URL, I then see x-litespeed-cache: hit.

    Interestingly, when I load the URLs with the Brave browser, this doesn’t happen, and for all URLs, I can see x-litespeed-cache: hit.

    This is a WordPress / WooCommerce installation on a server with elastic hosting and 6 CPU cores. In the .htaccess file, I have:

    <IfModule LiteSpeed>
    CacheEngine on esi crawler
</IfModule>

    But I’m not sure if something else is needed or if this setup is really correct.

    Has anyone encountered a similar problem?

    • This topic was modified 3 months, 1 week ago by GinaV.
Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Support qtwrk

    (@qtwrk)

    what was the other browser you used besides brave ?

    the CacheEngine on esi crawler directive will NOT work on .htaccess, it has to be set in Apache conf file

    and for our crawler, 201 indicates the page is cached

    Thread Starter GinaV

    (@ginavicente)

    I have done tests with browsers like Chrome and Firefox.

    Is the CacheEngine directive supposed to be configured by default in the Apache configuration file?

    If not, where can I find detailed instructions to do it from a CPanel.

    Thank you so much!

    Plugin Support qtwrk

    (@qtwrk)

    it is a directive controlled by the hosting provider or sys admin , cpanel user can not configure this option

    and also please do me a screenshot of your cralwer summary page

    Thread Starter GinaV

    (@ginavicente)


    Here is the screenshot
    https://ibb.co/kDVHZH6
    Thank you so much!

    • This reply was modified 3 months, 1 week ago by GinaV.
    Thread Starter GinaV

    (@ginavicente)

    Here is the screenshot
    https://ibb.co/kDVHZH6
    Thank you so much!

    Plugin Support qtwrk

    (@qtwrk)

    please provide the report number

    you can get it in toolbox -> report -> click “send to LiteSpeed”

    Thread Starter GinaV

    (@ginavicente)


    I just sent the report: KPMUFOHK

    Thread Starter GinaV

    (@ginavicente)

    At this point I have purged cache and am rerunning the crawlers

    Plugin Support qtwrk

    (@qtwrk)

    okay , please try randomly open a page in private widnow to check status , immediately after 4 crawlers finished , and do not do anything during the time in admin area like upgrade something , change some setting ..etc

    Thread Starter GinaV

    (@ginavicente)

    The crawlers takes approximately 1 hour to finish the entire process. As soon as I finish I will enter a URL to confirm the status and I will confirm what I have seen

    Thread Starter GinaV

    (@ginavicente)

    The crawlers is over. From this moment on, no changes have been made. I have visited several URLs at random. In all cases it happens as in the attached screenshot:

    https://ibb.co/ncjdzzg

    Plugin Support qtwrk

    (@qtwrk)

    that cookie looks suspecious

    could you please try remove anything that involves woo recent viewed product ?

    • This reply was modified 3 months, 1 week ago by qtwrk.
    Thread Starter GinaV

    (@ginavicente)

    Hello good evening,

    I just excluded that cookie, purged cache and ran crawlers again.

    Thanks a lot!!
    I’ll tell you how it went.

    Plugin Support qtwrk

    (@qtwrk)

    no no , don’t exclude it , when you set cookie exclude , that means to disable the cache at all , when such cookie is present

    please try remove the recent view widget/block , and then do the test

    Thread Starter GinaV

    (@ginavicente)

    Sorry, I didn’t interpret the message correctly. In any case, before purging the cache a while ago, I tested other URLs that do not contain woo recent viewed product, such static pages and blog articles and the cache problem was also present. In these cases that cookie was not found. I attached a screenshot:
    https://ibb.co/wrrJbPn

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.

Tags