Page Rules - Please help us understand


We would like to set up page rules to optimize our content delivery. New to Cloudflare, we have many questions. Your advice is greatly appreciated in advance:

  1. In Cache Level, if we choose bypass for the page, does it mean no cache will be performed to the defined page?

  2. What about Standard. Help us understand this scenario. If we choose not to add a page rule to the forum page, does it mean by default, member follows the cache setting we defined for the entire site? If so, why should we add a page rule to the member section, then choose standard as the cache level

  3. What does Cache Origin Control really mean?

  4. We are trying to debug an issue with login and logout.

  5. Our users some times have a hard time logging in. Some times they can not log out.

  6. This issue does not happen in our development environment.

  7. Presumably such login and logout is caused by cache set ups?

  8. To make sure we do not make matters worse, please help us understand these two features.

  9. Browser Cache TTL. If we include Browser Cache TTL and set like 1 hour as the value, does it mean the user cache will not expire in the next hour?

  10. Edge Cache TTL. If we set this to 1 hour, does it mean that each hour, the content on the edge server will be refreshed based on what new information we add to the site?

  11. If we try to use minify HTML, will it cause Cloudflare cache the page like a static, which could, in turn, interfere with user log in and log out?

1 Like


Page rules create exceptions to the default behavior for each setting. On Caching tab you set the cache level that applies to the whole zone, then on Page Rules you may want to set exceptions for subdirectories, subdomains, and even specific URLs. By default, Cloudflare does not cache HTML, only if you apply a PR to Cache Everything.

  1. Correct, but keep in mind that all assets requested by the defined page will still be cached. So: > bypass cache > won’t be cached but any files requested by it (CSS, JS, images etc) will. So the impact of PR to cache or bypass will be limited to the specified HTML.

  2. If you set a cache level to other than standard on the Caching tab of Cloudflare dashboard, you could want to set it to standard for specific areas with a page rule.

  3. You can set the Browser Expiration to “respect existing headers” on Caching tab.

9.) It means the browser will be instructed to keep the page on it’s cache for one hour.

  1. No. It means Cloudflare will keep a cache of the page on any of it’s datacenters that have actually received a hit for that page for 1 hour. After that time expires, if and when CF receives another visit to any of it’s datacenters, that datacenter will keep the page on its cache for another hour.

  2. No relation between minify HTML and caching. Cloudflare will only cache HTML if a Page Rule requires it.

This topic was automatically closed after 31 days. New replies are no longer allowed.