Add Page Rule Not To Cache Anything Inside WP-Admin

  • ResolvedPlugin Contributor iSaumya

    (@isaumya)


    4 years, 7 months ago

    Hi,
    First of all, I would like to say that I truly love this plugin and thank you very much for building it and moreover sharing it for free. I use this plugin on all of my client’s sites as it is my go-to plugin to set up caching for all the sites I work on.

    But while using this plugin across multiple sites one issue I have consistently noticed was that all the wp-admin/* pages are being cached as well as the ?swcfpc=1 parameter only gets appended to the front end URL but not for the WP admin URL.

    So, what ended up happening is that let’s say you make an update to the admin side, even after the update is done the page will show you the old data and the only way you can see the new data is by appending ?swcfpc=1 to the URL as it doesn’t get auto appended to the wp-admin URLs.

    You should definitely provide some mechanism to ensure anything inside wp-admin doesn’t use caching. As now I have to manually add a page rule in Cloudflare to make sure anything inside wp-admin is not cached. Please add this feature. Thanks again for the plugin.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Hi @isaumya ,
    first of all thank you for using this plugin ??

    This issue is somewhat strange. Have you enabled the option to disable the cache when a user is logged in and for AJAX requests?

    Please when you browse wp-admin/* open the Google Chrome console let me know if you see almost one of the following HTTP response headers:

    x-cf-wp-super-cache
x-cf-wp-super-cache-active

    and paste here their values.

    If you want I can check it by myself. Share the accesses and the URL by sending me a private email to salvatorefresta [at] gmail.com

    Bye

    Plugin Contributor iSaumya

    (@isaumya)

    This issue is somewhat strange. Have you enabled the option to disable the cache when a user is logged in and for AJAX requests?

    – Absolutely.

    No, I don’t see the headers mentioned above. Screenshot: https://i.imgur.com/Hw4VAj7.png

    Here are the headers that are coming off:

    
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: EXPIRED
cf-ray: 58027d7e1cf7f371-ATL
content-encoding: br
content-type: text/html; charset=UTF-8
date: Tue, 07 Apr 2020 08:48:33 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 11 Jan 1984 05:00:00 GMT
referrer-policy: strict-origin-when-cross-origin
server: cloudflare
status: 200
strict-transport-security: max-age=15552000; preload
vary: Accept-Encoding
x-content-type-options: nosniff
X-DNS-Prefetch-Control: off
x-frame-options: SAMEORIGIN
x-powered-by: centminmod
x-xss-protection: 1; mode=block

    Just to let you know that this site is hosted on an Nginx based server.

    I have also tested it on my other client sites which are running on LiteSpeed based cPanel server and here is response header for that:

    
alt-svc: h3-27=":443"; ma=86400, h3-25=":443"; ma=86400, h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
cache-control: max-age=5356800, must-revalidate
cf-cache-status: EXPIRED
cf-ray: 5802834f8f49c1c5-IAD
content-encoding: br
content-type: text/html; charset=UTF-8
date: Tue, 07 Apr 2020 08:52:32 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 11 Jan 1984 05:00:00 GMT
referrer-policy: strict-origin-when-cross-origin
server: cloudflare
status: 200
strict-transport-security: max-age=15552000; preload
vary: Accept-Encoding
x-content-type-options: nosniff
X-DNS-Prefetch-Control: off
x-frame-options: SAMEORIGIN
x-powered-by: PHP/7.4.4
x-turbo-charged-by: LiteSpeed

    So, maybe those headers only get added on Apache-based server?

    If you still need access to let me know, or if you need any other data, let me know.

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Hi dear,
    no, this does not depend on Nginx or Apache. Please update the plugin to version 3.3, purge the cache and try again to see if those headers appear.

    I have tested both on a server with only Nginx and on one with Apache in the backend. You should see the following header:

    x-wp-cf-super-cache: no-cache

    Let me know

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @salvatorefresta, yes I have tested with the latest update and after installing this new update it seems that the headers are now properly being added. Thank you for looking into this and fixing the issue.

    Thanks again for the awesome support.

    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    You’re welcome ??

    Hi

    Thank you for producing this great plugin. I have only recently installed it.

    Do I still need to use page rules or should I just leave everything to the plugin?

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @john53,
    Leave everything to the plugin. Remove all the page rules you have. The plugin will create the necessary rules as needed by itself.

    Hi Thats great thank you.

    I use the siteground optimizer plugin. It has static cache, dynamic cache and mem cache.

    Is it ok to leave all o theses activated or should I turn off some or all of them?

    Thank you very much.

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @john53,
    No you should deactivate them and use the fallback cache option inside our plugin.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Add Page Rule Not To Cache Anything Inside WP-Admin’ is closed to new replies.