x-qc-cache: miss even if crawler status=hit

  • Resolved Dan Di Gregorio

    (@mzarkoff)


    9 months, 3 weeks ago

    Hello,

    I’m encountering this problem, and I’ve seen that many others stumbled into it but none of the suggestions helped me, so I open a new ticket.

    I’ve finished to set up my litespeed plugin with QCloud enabled. The crawler finished to index all pages and all pages are cached but when I load those page in a browser or in a online tool the page header show x-qc-cache: miss the first time, and x-qc-cache: hit from the second time ahead.

    The same happens for all pages: the crawler reports “hit” for all of them but I have to load them twice to see Qcloud cache enabled.

    How can get rid of it?

    Here a screeshot for better documentation

    Dan

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

    (@qtwrk)

    please provide the report number

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

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Report number: BOKKFFDE

    Report date: 02/06/2024 09:50:54

    Plugin Support qtwrk

    (@qtwrk)

    please go to sitemap setting , set Drop Domain from Sitemap to OFF

    this is kind of normal , the crawler is meant to crawling on origin server but your origin is on apache , so it won’t work

    with this setting it will at least crawl on 1 CDN node

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Hello, thanks for your answer.

    I’ve changed the Drop Domain setting, reloaded the sitemap, re-launched the crawler but the problem still persists.

    Here the screenshot: https://prnt.sc/EYHR595sGiyr

    Plugin Support qtwrk

    (@qtwrk)

    yeah, that probably doesn’t work out , since you and server will redirect to different CDN , there is no fix unless you move to a LiteSpeed webserver

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    But I am on a litespeed webserver. My website is hosted by Scalahosting with Litespeed Server Enterprise.

    You can verify in headers response > https://prnt.sc/xVrVpenprfX9

    I am using the QUIC cloud DNS in order to avoid the CNAME setting in NS records, but I am on a Litespeed server for sure. Could the QUIC DNS cause this problem??

    Plugin Support qtwrk

    (@qtwrk)

    that only because you are hooked into the QUIC cloud CDN , without QC CDN, you should see it shows as Apache

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Here the webserver setting in my sPanel: https://prnt.sc/tzJz0IX9NFI6

    Anyway, I’ll restore the Scalahosting DNS to verify the headers responses and I’ll update this thread.

    Plugin Support qtwrk

    (@qtwrk)

    you can just go to QC dashboard, toggle “bypass CDN”

    you can check in LiteSpeed Cache -> Toolbox -> Report , check SERVER_SOFTWARE , at lease I see Apache from your report.

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Ok, it’s clear. Finally I think we’ve catch the problem. I’ll open a ticket with the hosting support and I’ll get back asap with news.
    Thanks a lot

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    The hosting support fixed this issue. Now the webserver is detected as “Litespeed” instead “Apache”. Both webserver was trying to run in the same time causing a conflict.

    Now I’ll make some test to provide a feedback soon in order to mark this request as “Fixed”, I hope….

    Dan

    Plugin Support qtwrk

    (@qtwrk)

    Please provide the report again, I’d like to double check

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Ok, my hosting provider fixed the webserver issue and now it appears as Litespeed, I’ve regenerated all the sitemap and launched the crawler for all pages, but….the problem seems to persist: https://prnt.sc/cKmSFhKMCef9

    Report number: KZJTAETW

    Plugin Support qtwrk

    (@qtwrk)

    okay , please set back that drop domain setting to ON , refresh sitemap and re-cralw

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    • Drop domain setting set to ON
    • Sitemap refreshed
    • Pages recrawled

    But the problem still persists: https://prnt.sc/uwIARpmNMqL-

    Report number: QAJAGGVQ

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘x-qc-cache: miss even if crawler status=hit’ is closed to new replies.