[FIX] CF-Cache-Status: DYNAMIC, or how make this plugin work

  • Resolved alx359

    (@alx359)


    4 years, 8 months ago

    Mind to other optimization lurkers like me that got stuck with CF-Cache-Status: DYNAMIC after installing and setting up everything as described.

    Installing this and the other “page cache” plugin, and uploading the Worker script into CF (free) wasn’t enough to make it work for me. I also had to add a “cache-everything” Page Rule in CF:

    Page Rule for domain.com

    URL matches: *domain.com/*

    Cache Level -- Cache Everything

    With certain plugins (like WP-Rocket) the above setting isn’t enough, and one may need to insert yet another setting to that same rule above:

    Edge Cache TTL -- 2 hours (or more)

    If not much at home with the Chrome’s Dev Console, can easily test if the response headers are as they should by opening a “Private Mode” window and checking this online tool over here:
    https://www.webconfs.com

    And how to measure speed improvements (mainly FBT), according a tool from the lead developer of the CF Worker script (Patrick Meenan):

    https://www.webpagetest.org

    HTH.

    • This topic was modified 4 years, 8 months ago by alx359.
Viewing 3 replies - 1 through 3 (of 3 total)

  • Technically your cache everything rule invalidates the entire workers script. This plugin is meant as a workaround to the lack of cookie bypass on free and pro accounts, since your page rule will cache everything from the admin bar to customer private data (on pages like my account, for example).

    Thread Starter alx359

    (@alx359)

    Yeah, think you’re right. As it wasn’t working, thought perhaps the script needed that rule and acted upon itself as yet another “limiting” rule, but later noticed it was caching the backend, so I gave up and uninstalled it.

    WP Cloudflare Super Page Cache is currently doing Workers in a beta and all looks quite nice. May contact the dev for the zip if you wish to help test it.

    I’ve been using Cache Everything for a while. Cloudflare advise you to set 2 x page rules to not cache Admin and Login pages then Cache Everything as the third rule.

    Regarding the HTML Edge Cache, if you’re using the API, don’t set up the KV Pair or it won’t work and vice versa. Use one or the other.

    Turn off the Cache Everything, as it’s not needed with this script.

    In the headers you should get:
    x-html-edge-cache-version: -1
    x-html-edge-cache-status: Hit
    x-html-edge-cache: cache,bypass-cookies=wp-|wordpress|comment_|woocommerce_

    When it doesn’t work you’ll usually just get the last one.

    • This reply was modified 4 years, 7 months ago by David Elstob.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[FIX] CF-Cache-Status: DYNAMIC, or how make this plugin work’ is closed to new replies.