“Expires” and “cache-control” issues

  • Resolved minhduc

    (@ducpl)


    5 years ago

    My site is experiencing this problem (expires: Wed, 11 Jan 1984 05:00:00 GMT)
    Please help me, thank you

    alt-svc: quic=”:443″; ma=2592000; v=”35,39,43,44″
    cache-control: no-cache, must-revalidate, max-age=0
    cf-railgun: 108c1ad6d5 0.05 0.003032 0030 57da
    cf-ray: 4be424abede4c6ba-HAN
    content-encoding: br
    content-type: text/html; charset=UTF-8
    date: Wed, 27 Mar 2019 20:34:07 GMT
    expires: Wed, 11 Jan 1984 05:00:00 GMT
    pragma: no-cache
    referrer-policy: no-referrer-when-downgrade
    server: cloudflare
    server-name: PL-01
    status: 200
    strict-transport-security: max-age=15768000; preload
    vary: User-Agent
    x-content-type-options: nosniff
    x-frame-options: SAMEORIGIN
    x-litespeed-cache: hit,private
    x-permitted-cross-domain-policies: none
    x-turbo-charged-by: LiteSpeed

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

    (@qtwrk)

    5 years ago

    Hi,

    That’s normal default WP behavior for login user , regardless if you have LSCWP installed or not, that is to prevent login user get browser cached data.

    Best regards,

    Thread Starter minhduc

    (@ducpl)

    5 years ago

    Hello @qtwrk ,

    I tried in an unregistered web browser. But it still appears (expires: Wed, 11 Jan 1984 05:00:00 GMT) Does that affect the litespeed’s cache, thanks.

    Plugin Support qtwrk

    (@qtwrk)

    5 years ago

    Hi,

    If you look at WP source code you will see it comes from WP itself.

    No , this won’t interfere with LiteSpeed Cache.

    Best regards,

    Thread Starter minhduc

    (@ducpl)

    5 years ago

    ok . thank you

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘“Expires” and “cache-control” issues’ is closed to new replies.