Test cache not working

  • Resolved frenchomatic

    (@frenchomatic)


    3 months ago

    WordPress version 6.6.1 Disk cache is not enabled and cloudflare caching set to on. Testing the cache and I get a green tick but it says undefined. It doesn’t say it is working as per your previous version. When I look at the response headers, I get a 200 with x-wp-cf-super-cache: cache x-wp-cf-super-cache-active: 1. However CF-Cache-Status: DYNAMIC.

    I also note the page rule has been removed in cloudflare and you are now only using cache rules. I use a special login url which is defined in your plugin under << Prevent the following URIs to be cached. >> . It doesn’t appear explicitly in the cloudflare admin panels cache rules. Do I need to add it?

    Also, by updating you have to turn cloudflare caching to on. This is a pain if you have lots of sites and want to simply update them all.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author optimole

    (@optimole)

    Thanks for a such detailed feedback.

    I could replicate the undefined error and we’re working to fix that, page rules are being deprecated by Cloudflare and we migrated to cache rules, but they should work just fine.

    I can’t replicate the fact that you need to enable Cloudflare after the update.

    Thread Starter frenchomatic

    (@frenchomatic)

    Basically, I can’t get it to work unless I add in the page rule. I don’t get a CF-Cache-Status HIT and only get CF-Cache-Status DYNAMIC. When I roll back the plugin with the page rule in place it works fine. Like this

    https://www.mydomain.com/* Cache Level:?Cache Everything

    Thread Starter frenchomatic

    (@frenchomatic)

    Just a thought but the first filter defined is << hostname equals domain.com >> . I agree this should work but it doesn’t for me . It seems to be a problem. Why not use URI full and a wildcard as the first filter with all the accompanying ANDs? The cache status is then a HIT. Like this URI wildcard https://*.mydomain.com/*.

    Thread Starter frenchomatic

    (@frenchomatic)

    I am closing this as you have effectively recognised the issue in another thread. Thanks for a great plugin and your responsiveness.

    Thread Starter frenchomatic

    (@frenchomatic)

    The behaviour where cloudflare caching needs to be enabled is still an issue in version 5.1. several people have mentioned this. A function in the next plugin to test where a url is a HIT or MISS would be useful too. I don’t know how you might integrate this.

    • This reply was modified 2 months, 4 weeks ago by frenchomatic.
    Plugin Author optimole

    (@optimole)

    I noted down your suggestion to easily expose the HIT/Miss without checking the headers. @frenchomatic

    As of having to enable cloudflare cache after each update, is this something with the new versions? You need to connect again or just enable?

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.