“we set the cache-control max-age=0 value for the nHTML file through the set of ModExpires rules we add in the htaccess file.
See: Reference: .htaccess Rules
– Yes forgot to tell you about that. I thought they were setting it at the PHP level. Removing the WP Rocket htaccess rules was important. I thought they auto removed it on disabling cache.
I activated Add browser caching rules for static assets, Auto prefetch URLs in viewport, Auto prefetch URLs on mouse hover. Would love to get any farther tips/todo from you.
– All good. Make sure Tiered Cache is turned on in the CF Dashboard and do not use any other page rule or worker to modify the cache behavior in any way. Let the plugin handle your cache. Also inside the CF Dashboard > Caching > Settings make sure Browser Caching TTL is set to Response Header and do not add any page rule to tinker with cache behaviour.
I still need to find what is causing response cookies.
– What response cookie? I have not seen any response cookies in your page. Can you share a page URL where the cookie is present? As looking at the cookie name might help what is adding that cookie.