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

    (@qtwrk)

    Hi,

    LiteSpeed Cache plugin has its own crawler for pre-cache the pages

    Best regards,

    Thread Starter kdfr

    (@kdfr)

    Hi @qtwrk,

    thank you very much, but my search for a working Warm Cache Cralwer resulted from this:

    LiteSpeed Crawler is disabled on most shared hosts.

    Ok., can’t be changed.

    Best regards

    Thread Starter kdfr

    (@kdfr)

    I have now run Purge All-LSCache in the LiteSpeed ??Cache Toolbox
    and then checked it with LSCache Check.

    The display is: X-Litespeed-Cache: miss

    Then I let the warm cache run and the LCCache check showed: X-LiteSpeed-Cache: hit

    This measurement shows the correct result and the desired function of the cache.

    Plugin Support qtwrk

    (@qtwrk)

    I’m sorry ?

    if it works as desired, then what is the issue?

    Thread Starter kdfr

    (@kdfr)

    Hi @qtwrk,

    the problem is:
    Although the warmCache crawler is running, which is confirmed by the LSCache check, the TTFB is approx. 500 ms when it is first called and only approx. 50 ms when it is called afterwards.
    The last line in the page source text with the current time is only displayed when the website is called up in the browser:
    <! – Page generated by LiteSpeed ??Cache 3.6.4 on 2021-04-05 09:04:58 ->
    The time when the WarmCache Crawler first visited the site is not displayed.

    Best regards,

    Plugin Support qtwrk

    (@qtwrk)

    Hi

    Please try make your own crawler to mimic full Chrome header

    Best regards,

    Thread Starter kdfr

    (@kdfr)

    Hi @qtwrk,

    Thank you for your kind and persistent support.
    Unfortunately, my specialist knowledge is no longer sufficient to carry out further steps.
    Perhaps one day there will still be a crawler in the Litespeed cache that can run independently of the hoster.

    Best regards!

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I am not sure how your crawler works , but a reasonable expectation is that it should be able to send out certain user agent

    like chrome has UA like Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36

    this needs to be send alone with crawler to the server to make it (pre)cache for Chrome browser

    Best regards,

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Keeping cache warm’ is closed to new replies.