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

  • Resolved Dan Di Gregorio

    (@mzarkoff)


    1 year, 1 month 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 6 replies - 16 through 21 (of 21 total)
  • Plugin Support qtwrk

    (@qtwrk)

    actually it shows it works as my screenshot

    the crawler will crawl at origin server and origin server is giving hit

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    So, it could be normal that x-qc-cache returns “miss” in a guest first visit?

    Plugin Support qtwrk

    (@qtwrk)

    yes , where it shows x-litespeed-cache: bkd it means the page is served by cache from origin server

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Ok, so just to understand better: when the page will be served by the closest QC pop to the guest visitors? This is important to reduce the TTFB.

    Plugin Support qtwrk

    (@qtwrk)

    when that pop is being accessed by someone

    Thread Starter Dan Di Gregorio

    (@mzarkoff)

    Ok, I still have to understand completely the plugin functionality with QC but I close this thread as Resolved. Thanks a lot for your patience and assistance.

    Dan

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