“Do Not Cache URIs” issue on WPMU sub-sites

  • Resolved Qtwix

    (@albiurs)


    7 years, 7 months ago

    Hi,

    I have “primary site configs for all subsites” set in network admin.
    And on the primary site, I configured “Do Not Cache URIs”, excluding:
    /wp-admin/upload.php

    However, this works on the primary site only but not on the sub-sites within the same WPMU installation, as this string is not replicated to the sub-site’s according “Do Not Cache URIs” field at all. See screenshots at:
    https://www.dropbox.com/sh/y6cwdt0qbdgxhjs/AABjby8ts60LwrLkR3ryQGAMa?dl=0
    …the according field is empty, but I actually would expect that this field contains the same string/s as the primary site’s “Do Not Cache URIs” field. According to the missing string/s, it’s clear that the exclusion just works on the primary site but not on the sub-sites.

    I guess, this is a bug in the plugin.

    Thanks in advance for fixing.

    Best regards,
    Urs

    • This topic was modified 7 years, 7 months ago by Qtwix.
Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support qtwrk

    (@qtwrk)

    7 years, 7 months ago

    Hi,

    If I remember correctly , these login and admin page were not cached anyway.

    Do you see “x-litspeed-cache-control: no-cache” header on subsite page?

    Best regards,

    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    Hi,

    There’s an option Cache > “Cache Logged-in Users”. I it’s turned on, then I have caching issues in the media library with the additional plugin “WP Real Media Library”, which shows additional folders in the library; “Purge All” resolves the issue. If I turn Cache > “Cache Logged-in Users” off then I don’t have any caching issue. So I assume, the backend is actually cached and therefore, I want to exclude the media library from being cached.

    Where do I find this “x-litspeed-cache-control: no-cache” header on subsite page?

    Thanks!

    Best regards

    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    …I uploaded an additional screencast to the folder to outline better, what I mean:
    https://www.dropbox.com/sh/y6cwdt0qbdgxhjs/AABjby8ts60LwrLkR3ryQGAMa?dl=0&preview=caching_issue.mp4

    Thanks!

    • This reply was modified 7 years, 7 months ago by Qtwix.
    Plugin Support qtwrk

    (@qtwrk)

    7 years, 7 months ago

    Hi,

    You can press F12 to open browser dev tool , and on network tab you will see request/response header.

    there is an option box in tab 4 Exclude , “do not cache URI” please try add “wp-admin” to that field , save it , and purge all , see how it goes.

    Best regards,

    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    Hi,

    So I checked the header and while the frontend correctly shows “x-litespeed-cache: hit”, the backend below wp-admin shows a hader with “x-litspeed-cache-control: no-cache”. However, the issue is still present using the suggested “wp-admin” string in “do not cache URI”, as shown in my video linked above.

    -> So, I’m I right that if I get “x-litspeed-cache-control: no-cache” in the header while loading the backend, it means that LiteSpeed Cache does not cache the page at all?
    -> And if yes, how come that the LS Cache setting “Logged-in Users” on/off as well as purging the cache influences the backend as shown in the linked video?

    Thanks,
    Urs

    Plugin Support qtwrk

    (@qtwrk)

    7 years, 7 months ago

    Hi,

    1. Yes, when you see “x-litespeed-cache-control: no-cache” measn no cache , it’s passed and processed by PHP itself.

    2. Cache login page are meant for front page, not wp-admin area.

    Please submit a ticket here, seems we need to dig it deeper.

    Best regards,

    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    Hi,

    I just wanted to submit a ticket as you suggested. However, since I upgraded the LiteSpeed Cache plugin yesterday, I cannot reproduce the issue anymore. So it seems as if the update resolved the issue. So, in case I will experience the issue again, I will get back here.

    Thanks

    Plugin Support qtwrk

    (@qtwrk)

    7 years, 7 months ago

    Hi,

    Please keep us posted 🙂

    Best regards,

    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    Hi,

    Unfortunately, the issue is back again. I’ll contact my host first and if the issue persists, I’ll pass it to the LS support as you suggested in the previous post.

    Best regards,

    • This reply was modified 7 years, 7 months ago by Qtwix.
    • This reply was modified 7 years, 7 months ago by Qtwix.
    Thread Starter Qtwix

    (@albiurs)

    7 years, 7 months ago

    Hi,

    I finally found the error. It’s not the LS Cache which causes the issue, it’s browser related. The issue was caused by the browser cache of Firefox, if it’s not executed in private mode. Running Firefox in private mode removes the issue.

    Thanks anyway.

    Best regards,

    Plugin Support qtwrk

    (@qtwrk)

    7 years, 7 months ago

    Hi,

    Glad to know it’s figured out.

    I will mark this topic as solved now, please open a new topic if you have any further questions.

    Best regards,

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

The topic ‘“Do Not Cache URIs” issue on WPMU sub-sites’ is closed to new replies.