• Resolved lordsnake

    (@lordsnake)


    everything in my wpadmin is being cached, including the litespeed settings.
    So no matter what I changed, it just show sme the previous settings.

    I have purged everything and cleared my browser cache, but it still caching all pages.

    As a result I do not know what plugins actually need updating, as it is showing a cached page, and telling me plugins need updating which have already been updated.

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

    (@qtwrk)

    Hi,

    please check your HTTP response header on wp-admin pages

    by default LSCWP does NOT cache wp-admin , please check if you have any force cache setting

    also what is your server environment ? shared hosting or your own managed server ?

    Best regards,

    Thread Starter lordsnake

    (@lordsnake)

    it is shared hosting.
    What do you mean by “check if you have any force cache setting”

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I mean the options like these

    also please check your http response header on wp-admin pages , it should show “x-litespeed-cache-control: no-cache”

    Also did you enable object cache and opcache ?

    Best regards,

    danyjack7

    (@danyjack7)

    Hi,

    I have the same problem.
    I manage my own server with LiteSpeed server (OpenLiteSpeed).
    The settings you mentioned are blank.
    WP and the plugin are updated to the latest version.

    I disabled the object cache and opcache and I done a Purge All, but the problem is always there.

    Another thing I noticed is that every notification I have in the dashboard (for example updated plugin or cache purged), comes out when I change page and to remove it I have to refresh the page itself.

    Plugin Support qtwrk

    (@qtwrk)

    But what are response header you see on wpadmin page?

    danyjack7

    (@danyjack7)

    no-cache

    Plugin Support qtwrk

    (@qtwrk)

    Yeah well

    could you please post a more detailed, full header?

    danyjack7

    (@danyjack7)

    This is the result from the home page when I logged as admin:

    access-control-allow-origin: *
    alt-svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-25=":443"; ma=2592000, h3-27=":443"; ma=2592000
    cache-control: public, max-age=15552000
    content-encoding: gzip
    content-type: text/html; charset=UTF-8
    date: Sat, 07 Nov 2020 16:57:10 GMT
    expires: Wed, 11 Jan 1984 05:00:00 GMT
    link: <https://mysite.it/wp-json/>; rel="https://api.w.org/"
    link: <https://mysite.it/wp-json/wp/v2/pages/37429>; rel="alternate"; type="application/json"
    link: <https://mysite.it/>; rel=shortlink
    pragma: no-cache
    public-key-pins: pin-sha256="pin1"; pin-sha256="pin2"; max-age=2592000
    referrer-policy: strict-origin-when-cross-origin
    server: LiteSpeed
    status: 200
    vary: Accept-Encoding
    x-content-type-options: nosniff
    x-frame-options: SAMEORIGIN
    x-litespeed-cache-control: no-cache
    x-xss-protection: 1;mode=block
    Plugin Support qtwrk

    (@qtwrk)

    check these 2

    cache-control: public, max-age=15552000

    and

    x-litespeed-cache-control: no-cache

    LiteSpeed cache did NOT cache this page, but something else tell browser to cache the page for 15552000 seconds

    you need to get rid of that cache-control header

    danyjack7

    (@danyjack7)

    Now, I see the issue.

    I had followed this guide: How to set up custom headers in OpenLiteSpeed but the setting of the Header Operations give me this cache issue in wp-admin dasboard.

    I have removed this

    unset Cache-control
    set Cache-control public, max-age=15552000
    set Access-Control-Allow-Origin: *

    and now it is all ok.

    Thank you for your support!

    Plugin Support qtwrk

    (@qtwrk)

    well , I guess you might be missing the part

    exp:^.*(css|gif|ico|jpeg|jpg|js|png|webp|woff|woff2|fon|fot|ttf)$

    without this , it will apply to ALL URI , instead of these static file only ??

    danyjack7

    (@danyjack7)

    Oh dude, you are right! ??
    So can I set that up again? I mean this:

    unset Cache-control
    set Cache-control public, max-age=15552000
    set Access-Control-Allow-Origin: *
    Plugin Support qtwrk

    (@qtwrk)

    yes , but do EXACTLY as that guide state , don’t miss anything

    and double check you do NOT see cache-control header OTHER than static resources

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I’m going to mark this topic “Resolved”, due to lack of activity.

    If you still need help, please feel free to re-open it.

    Best regards,

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘WPADMIN being cached’ is closed to new replies.