Use with Litespeed

  • fzoi77

    (@fzoi77)


    4 years, 6 months ago

    When used longitudinally with Litespeed, the header looks like this Is this correct?

    alt-svc: h3-27=":443"; ma=86400, h3-25=":443"; ma=86400, h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
cache-control: no-cache, must-revalidate, max-age=0
cf-cache-status: REVALIDATED
cf-ray: 595579590d120b8b-NRT
cf-request-id: 02c94a2ba500000b8bd280b200000001
content-encoding: br
content-type: text/html; charset=UTF-8
date: Mon, 18 May 2020 12:10:15 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
link: <https://fmoga.com/wp-json/>; rel="https://api.w.org/"
server: cloudflare
status: 200
vary: Accept-Encoding
x-cacheable: yes
x-litespeed-cache: hit,private
x-turbo-charged-by: LiteSpeed
x-wp-cf-super-cache: cache
x-wp-cf-super-cache-active: 1

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter fzoi77

    (@fzoi77)

    4 years, 6 months ago

    If you set “Overwrite the cache-control header for WordPress’s pages using web server rules” to YES, the header will be switched as shown below.

    However, “cf-cache-status: HIT” appears on the admin page too, and the admin page is not bypassed.

    age: 170
alt-svc: h3-27=":443"; ma=86400, h3-25=":443"; ma=86400, h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
cache-control: s-max-age=604800, s-maxage=604800, max-age=60
cf-cache-status: HIT
cf-ray: 595668f6dc71d62d-NRT
cf-request-id: 02c9dfee420000d62d7d03e200000001
content-encoding: br
content-type: text/html; charset=UTF-8
date: Mon, 18 May 2020 14:53:50 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
link: <https://fmoga.com/wp-json/>; rel="https://api.w.org/"
server: cloudflare
status: 200
vary: Accept-Encoding
x-cacheable: yes
x-litespeed-cache: miss
x-litespeed-cache-control: private,max-age=1800
x-litespeed-tag: add_tag_priv,public:add_HTTP.200,public:add_home,public:add_URL.6666cd76f96956469e7be39d750cc7d9,public:add_F,public:add_
x-turbo-charged-by: LiteSpeed
x-wp-cf-super-cache: cache
x-wp-cf-super-cache-active: 1
    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    4 years, 6 months ago

    Hi @fzoi77 ,
    I know about this issue. Seems that litespeed server ignores the expr directive in htaccess. I’m working on a solution. Do you want test a beta version to see if it works on your environment?

    If yes, drop me an email and I will send it to you

    Thread Starter fzoi77

    (@fzoi77)

    4 years, 6 months ago

    OK.
    We contacted you through your website.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Use with Litespeed’ is closed to new replies.