2 status codes & no cache-control in response header

  • Resolved breadf

    (@breadf)


    7 months, 4 weeks ago

    Hi,

    I noticed 2 issues in console:

    1. A lot of product archive pages have 2 status code: 301 and 200, but they are same url, except the query string “?_gl=*****”. The 301 code url would delay the load for about 1s. How to solve this?
    2. Another is “cache-control” for html. I’ve set up “Default Public Cache TTL: 604800”, “Default Private Cache TTL: 1800″…… However there is no cache-control for html in response header. Is this normal?

    I assume the TTL in quic.cloud should align with my settings in litespeed cache -> cache -> TTL, is that right?

    Here is a video record for viewing: https://www.loom.com/share/c3003774d0a74bd7bbeea53105853a7f?sid=6651eb7b-9bbd-4c11-be5f-b2bbcf1520bc

    • This topic was modified 7 months, 4 weeks ago by breadf.

    The page I need help with: [log in to see the link]

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

    (@qtwrk)

    7 months, 4 weeks ago

    the ?_gl is not coming from us , looks like some kind of campaign or statistic related stuff

    no , you probably won’t see it when beyond QC , otherwise it will be like this

    not completely , it will try stay on node as longer as possible , but it is not completely follow the TTL , depends on traffic and node capacity

    Thread Starter breadf

    (@breadf)

    7 months, 4 weeks ago

    @qtwrk The query string “?_gl” is added by google. I’ve set “Drop Query String” to drop this query string.

    Is the html loaded in 301 code from stale cache, as “Serve Stale” is turned on in cache -> purge?

    If it’s not from stale cache, how to avoid this extra page load?

    Plugin Support qtwrk

    (@qtwrk)

    7 months, 3 weeks ago

    no , serve stale doesn’t work that way

    try check the http response header, it may give some clue who initiated or did that redirection

    Thread Starter breadf

    (@breadf)

    7 months, 3 weeks ago

    Below is the response header for the unnecessary redirection. Please help check and enlighten me.

    cache-control no-cache, must-revalidate, max-age=0, private

    content-length 0

    content-type text/html; charset=UTF-8

    date Fri, 17 Oct 2025 01:00:58 GMT

    location https://antzracing.com/product-category/car-types/desert-truck/?_gl=1%2Acwgpd9%2A_up%2AMQ..%2A_ga%2AMTUyOTcwNDUzNi4xNzYwNjYyODUz%2A_ga_N37CYRD7Y2%2AczE3NjA2NjI4NTIkbzEkZzAkdDE3NjA2NjI4NTIkajYwJGwwJGgxNzcwMjAwNjI3

    server LiteSpeed

    vary Accept-Encoding

    x-dns-prefetch-control on

    x-litespeed-cache-control no-cache

    x-litespeed-tag 457_WC_T.151,457_WC_T.155

    x-qc-pop AS-HK-HKG-125

    x-redirect-by WordPress

    Plugin Support qtwrk

    (@qtwrk)

    7 months, 3 weeks ago

    what was source URL ?

    Thread Starter breadf

    (@breadf)

    7 months, 3 weeks ago

    Hi @qtwrk,

    It happens only in a few urls, not all, and mostly in product archive pages. For example: https://(site domain)/product-category/all-parts/suspension/

    Note: in below video, this url has redirection, but when I tried in a different browser, the redirection disappeared.

    Please check the video record: https://www.loom.com/share/507899f40369489e874a434e97d391b5

    Plugin Support qtwrk

    (@qtwrk)

    7 months, 3 weeks ago

    x-redirect-by WordPress

    well, I can only tell something from the worpdress did that redirection , but I can’t tell what did it

    Thread Starter breadf

    (@breadf)

    7 months, 3 weeks ago

    ok. Thanks

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘2 status codes & no cache-control in response header’ is closed to new replies.