• Anonymous User 9018418

    (@anonymized-9018418)


    Will this plugin work fine if I set Edge Cache TTL in CloudFlare caching rule?
    AFAIK, when Edge Cache TTL is used with the “Cache all” rule, it leads to some changes in how CloudFlare strips the cookies from responses. But I haven’t researched the details of this scenario yet. Maybe you already know and tested it?
    I’d love to use as long as possible TTL for Edge Cache and set it up from the plugin.
    If it should work fine, could you please add a setting for Edge Cache TTL?
    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi @mr-13,

    Will this plugin work fine if I set Edge Cache TTL in CloudFlare caching rule?

    – No it won’t. Don’t set that. It is set by the plugin. You can also change the value inside plugin settings (cache tab). In Cloudflare cache, it must need to be Respect Existing Header.

    it leads to some changes in how CloudFlare strips the cookies from responses.

    – Cloudflare never strips any cookie from responses. When CF seen a cookie in response header it does not cache that page thinking the cookie value might be used to dynamically change the page data.

    When using the plugin, don’t tinker with CF edge cache TTL and just have a 1-page rule automatically added by the plugin to cache everything. Do not keep any other page rules to alter caching in CF. As everything is handelled by the plugin itself. You just need that 1 page rule which is added by the plugin. Rest the plugin will handle on it’s own.

    You can use CF page rules or other things like forwarding URLs etc.

    But I haven’t researched the details of this scenario yet. Maybe you already know and tested it?

    – Use the plugin and you will see on your own.

    could you please add a setting for Edge Cache TTL?

    – It’s already there. Please use the plugin and check the FAQ tab. Screenshot: https://i.imgur.com/vltwI6L.png

    Thread Starter Anonymous User 9018418

    (@anonymized-9018418)

    Cloudflare never strips any cookie from responses. When CF seen a cookie in response header it does not cache that page thinking the cookie value might be used to dynamically change the page data.

    Docs saying the opposite:

    When combined with an Edge Cache TTL > 0, Cache Everything removes cookies from the origin web server response.

    https://support.cloudflare.com/hc/en-us/articles/218411427-What-does-edge-cache-expire-TTL-mean-#summary-of-page-rules-settings

    Anyways, I’ve read CloudFlare docs and found all the answers to my questions.

    From the interface of the plugin, it was not clear that the “Cache-Control” header also affects Edge Cache TTL, but this article cleared it up.

    Thanks for the plugin, btw.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Edge Cache TTL setting and compatibility’ is closed to new replies.