x-qc-cache: miss

  • Resolved Egl

    (@egletiere)


    11 months, 3 weeks ago

    Hi!

    I would really appreciate some help with the following issue:

    I have set up a Woocommerce website that uses WPML (configured with separate domains for each language) and LiteSpeed Cache with active Redis Extension.

    quic.cloud CDN services are also active with Cache disabled (breaks site). Only Europe and North America are allowed through traffic filters.

    Even though in my opinion the cache service works fine, I noticed that I get “x-qc-cache: miss” in the headers and ” LSCache is supported” on LSCache Check.

    Is this normal behaviour? Shouldn’t I get a “hit”?

    Any advice is appreciated. Thanks!

    Report number: IKAAPKHN

    Report date: 04/05/2024 06:10:55

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

    (@qtwrk)

    yes, with WPML/WCML , the first access will be miss , in order to properly set cookie for currency/language.

    Thread Starter Egl

    (@egletiere)

    The issue is that not only the first access is a miss. There is no hit, no matter how many times the page is accessed.

    Plugin Support qtwrk

    (@qtwrk)

    how so ?

    I can see x-litespeed-cache: bkd

    Thread Starter Egl

    (@egletiere)

    I was referring to the “x-qc-cache: miss” which happens every time, not only at the first access. Shouldn’t I get a “hit”?

    Plugin Support qtwrk

    (@qtwrk)

    you set enable cache in QC dashboard to OFF, then you will see x-qc-cache miss all the time

    Thread Starter Egl

    (@egletiere)

    Good point. I understand. Thank you!

    Is there anything I can do about the fact that activating Cache in the QC dashboard messes up some pages after a few hours?

    Plugin Support qtwrk

    (@qtwrk)

    logically , the local lscache should be same as qc cache

    do you see any error message or warning when that happens in browser dev tool console ?

    Thread Starter Egl

    (@egletiere)

    I did not check for error when the issue happened and I cannot reproduce it right now. All seems good for the moment so I will close the ticket and open a new one if necessary. Thank you for your support!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘x-qc-cache: miss’ is closed to new replies.