cf-cache-status is DYNAMIC

  • Resolved windorz

    (@windorz)


    1 month ago

    In a situation where the plugin is enabled and Cache Rules have been added to Cloudflare, the cache for dynamic pages is set to DYNAMIC.

    However, when I change the Edge TTL option in Cache Rules to “Use cache-control header if present, use default Cloudflare caching behavior if not: If a cache-control header is present on the response, follow its directives. If not, cache in accordance with our default edge TTL settings,”

    the cache becomes a HIT.

    Is this the correct behavior?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter windorz

    (@windorz)

    After trying various things, I found that when the cf-cache-status is DYNAMIC and the cache is not being stored, changing the Edge TTL option and saving it makes the cache start hitting. Even after reverting the Edge TTL option back, it does not return to DYNAMIC.

    I believe this is likely not a problem with the plugin, but rather an issue on the Cloudflare side.

    Thread Starter windorz

    (@windorz)

    found the cause.

    Even after logging out of my site, the following cookies remained:

    • wordpress_logged_in_
    • wordpress_sec_

    After deleting these cookies, the cache changed from DYNAMIC to HIT, regardless of the Edge TTL settings.

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