Page Rules migration guide

Context:

You configured a Page Rule to perform an automatic redirect from HTTP to HTTPS for all subdomains of example.com and the example.com domain itself:

• URL *example.com/*
• Setting: Always Use HTTPS

How to migrate:

1. Create a dynamic redirect to always redirect HTTP requests to HTTPS for any hostname that contains example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com" AND SSL/HTTPS is off
     • Using the Expression Editor:
       (http.host contains "example.com" and not ssl)

   • Then:

     • Type: Dynamic
     • Expression: concat("https://", http.host, http.request.uri.path)
     • Status code: 301

2. Turn off your existing Page Rule and validate the behavior of the redirect you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Automatic HTTPS Rewrites for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Automatic HTTPS Rewrites
• Value: On

How to migrate:

1. Create a configuration rule to always rewrite HTTP links to HTTPS for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Automatic HTTPS Rewrites
     • Value: On

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule adjusting browser cache TTL to one day for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Browser Cache TTL
• Enter Browser Cache TTL: a day

How to migrate:

1. Create a cache rule to adjust browser cache TTL for caching resources in the browser to one day for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Browser TTL: Override origin and use this TTL
     • Input time-to-live (TTL): 1 day

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Browser Integrity Check for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Browser Integrity Check
• Value: On

How to migrate:

1. Create a configuration rule to turn on Browser Integrity Check for protecting against bots and threats for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Browser Integrity Check
     • Value: On

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Bypass Cache on Cookie for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Bypass Cache on Cookie
• Enter value: test_cookie

How to migrate:

1. Create a cache rule to bypass cache for requests containing cookie test_cookie for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com" AND Cookie contains "test-cookie"
     • Using the Expression Editor:
       (http.host contains "example.com" and http.cookie contains "test-cookie")

   • Then:

     • Cache eligibility: Bypass cache

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Cache By Device Type for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Cache By Device Type
• Value: On

How to migrate:

1. Create a cache rule to cache content based on user agent or device type for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Cache key
       • Cache by device type: On

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Cache Deception Armor for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Cache Deception Armor

How to migrate:

1. Create a cache rule to protect against cache deception attacks for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Cache key
       • Cache deception armor: On

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on caching of all assets for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Cache Level
• Select Cache Level: Cache Everything

How to migrate:

1. Create a cache rule to adjust cache level for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on caching for responses that contained cookie test-cookie for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Cache on Cookie
• Enter value: test-cookie

How to migrate:

1. Create a cache rule to cache responses containing cookie test_cookie for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com" AND Cookie contains "test-cookie"
     • Using the Expression Editor:
       (http.host contains "example.com" and http.cookie contains "test-cookie")

   • Then:

     • Cache eligibility: Eligible for cache

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on caching of every response with status code between 200 and 599 for one day, for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Cache TTL by status code
• Status code or enter range: 200-599
• Select option: a day

How to migrate:

1. Create a cache rule to cache responses with status code between 200 and 599 for one day for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Edge TTL
       • Use cache-control header if present, use default Cloudflare caching behavior if not
       • Status code TTL:
         • Scope: Range
         • From: 200
         • To: 599
         • Duration: 1 day

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule setting a custom cache key for all query string parameters, for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Custom Cache Key
  • Query String: All query string parameters

How to migrate:

1. Create a cache rule to set a custom cache key for all query string parameters, for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Cache key
       • Query string: All query string parameters

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Cloudflare Apps (deprecated) for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Disable Apps

How to migrate:

1. Create a configuration rule to disable Cloudflare Apps (deprecated) for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Disable Apps

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule with Disable Performance (deprecated) for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Disable Performance

How to replace:

1. Create a configuration rule to disable Mirage, Polish, and Rocket Loader for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Mirage: Off
     • Polish: Off
     • Rocket Loader: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule with Disable Security (deprecated) for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Disable Security

This setting turned off a subset of Cloudflare security features: Email Obfuscation, Rate Limiting (previous version), Scrape Shield, Server Side Excludes, URL (Zone) Lockdown, and WAF managed rules (previous version).

How to replace:

1. Create a configuration rule to turn off one or more security features:

   • Email Obfuscation (part of Cloudflare Scrape Shield)
   • Server Side Excludes, now deprecated (part of Cloudflare Scrape Shield)
   • Hotlink Protection (part of Cloudflare Scrape Shield)

2. If required, create a WAF exception to skip one or more rules of WAF managed rulesets for requests coming from IP addresses in an allowlist.

3. Turn off your existing Page Rule and validate the behavior of the rules you created.

4. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Zaraz for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Disable Zaraz

How to migrate:

1. Create a configuration rule to turn off Zaraz for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Disable Zaraz

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule adjusting Edge Cache TTL for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Edge Cache TTL
• Enter Edge Cache TTL: a day

How to migrate:

1. Create a cache rule to adjust edge cache TTL for caching resources on Cloudflare edge to one day, for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Edge TTL
       • Ignore cache-control header and use this TTL
       • Input time-to-live (TTL): 1 day

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Email Obfuscation for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Email Obfuscation
• Value: Off

How to migrate:

1. Create a configuration rule to turn off Email Obfuscation for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Email Obfuscation
       • Value: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule permanently redirecting www.example.com to example.com on all URI paths:

• URL: www.example.com/*
• Setting: Forwarding URL
• Select Status code: 301 - Permanent Redirect
• Destination URL: https://example.com/$1

How to migrate:

1. Create a dynamic redirect to permanently redirect requests from www.example.com to example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname equals "www.example.com"
     • Using the Expression Editor:
       (http.host eq "www.example.com")

   • Then:

     • Type: Dynamic
     • Expression: concat("https://example.com", http.request.uri.path)
     • Status code: 301

2. Turn off your existing Page Rule and validate the behavior of the redirect you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule permanently redirecting example.com/old-path to example.com/new-path:

• URL: example.com/old-path/*
• Setting: Forwarding URL
• Select Status code: 301 - Permanent Redirect
• Destination URL: https://example.com/new-path/$1

How to migrate:

1. Create a dynamic redirect to permanently redirect requests for example.com/old-path to example.com/new-path:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname equals "example.com" AND URI Path starts with "/old-path/"
     • Using the Expression Editor:
       (http.host eq "example.com" and starts_with(http.request.uri.path, "/old-path/"))

   • Then:

     • Type: Dynamic
     • Expression: concat("/new-path/", substring(http.request.uri.path, 10))
       (where 10 (start byte value) is the length of /old-path/)
     • Status code: 301

2. Turn off your existing Page Rule and validate the behavior of the redirect you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule changing the Host HTTP header to example.saas-provider.com, for all requests addressed at any subdomain of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Host Header Override
• Enter value: example.saas-provider.com

How to migrate:

1. Create an origin rule changing the Host header to example.saas-provider.com for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Set origin parameters:
       • Host Header > Rewrite to: example.saas-provider.com

2. Turn off your existing Page Rule and validate the behavior of the origin rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule adding a CF-IPCountry HTTP header, for all requests addressed at any subdomain of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: IP Geolocation Header
• Value: On

How to migrate:

1. Turn on the Add visitor location headers Managed Transform — a Transform Rules feature — to add the CF-IPCountry and other location headers to all requests.
2. Turn off your existing Page Rule and validate the behavior of the Managed Transform.
3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Mirage for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Mirage
• Value: Off

How to migrate:

1. Create a configuration rule to turn off Mirage for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Mirage
       • Value: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Opportunistic Encryption for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Opportunistic Encryption
• Value: Off

How to migrate:

1. Create a configuration rule to turn off Opportunistic Encryption for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Opportunistic Encryption
       • Value: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Origin Cache Control for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Origin Cache Control
• Value: Off

How to migrate:

1. Create a cache rule to determine edge cache behavior for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Origin Cache Control
       • Enable Origin Cache Control: Off

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Origin Error Page Pass-thru for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Origin Error Page Pass-thru
• Value: On

How to migrate:

1. Create a cache rule to determine edge cache behavior for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Origin error page pass-thru
       • Use Origin error page pass-thru: On

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Polish for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Polish
• Value: Off

How to migrate:

1. Create a configuration rule to turn off Polish for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Polish
       • Select value: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on Query String Sort for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Query String Sort
• Value: On

How to migrate:

1. Create a cache rule to sort query string parameters for caching purposes, for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Cache key
       • Sort query string: On

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule changing the origin to example.saas-provider.com, for all requests addressed at any subdomain of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Resolve Override
• Enter value: example.saas-provider.com

How to migrate:

1. Create an origin rule overriding the origin to example.saas-provider.com for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • DNS Record > Override to: example.saas-provider.com

2. Turn off your existing Page Rule and validate the behavior of the origin rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning on byte-for-byte equivalency checks for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Respect Strong ETags
• Value: On

How to migrate:

1. Create a cache rule to respect strong ETags for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then:

     • Cache eligibility: Eligible for cache
     • Setting: Respect strong ETags
       • Use strong ETag headers: On

2. Turn off your existing Page Rule and validate the behavior of the cache rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule turning off Rocket Loader for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Rocket Loader
• Value: Off

How to migrate:

1. Create a configuration rule to turn off Rocket Loader for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Rocket Loader
       • Value: Off

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule setting Security Level to I’m Under Attack for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: Security Level
• Select Security Level: I’m Under Attack

How to migrate:

1. Create a configuration rule to set Security Level to I’m Under Attack, for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: Security Level
       • Select Security Level: I’m Under Attack

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule adding a True-Client-IP HTTP header for all requests addressed at any subdomain of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: True Client IP Header
• Value: On

How to migrate:

1. Turn on the Add “True-Client-IP” header Managed Transform — a Transform Rules feature — to add the True-Client-IP header to all requests.
2. Turn off your existing Page Rule and validate the behavior of the Managed Transform.
3. If your tests succeed, delete the existing Page Rule.

Context:

You configured a Page Rule setting SSL to Strict for all subdomains of example.com and the example.com domain itself:

• URL: *example.com/*
• Setting: SSL
• Select SSL/TLS encryption mode: Strict

How to migrate:

1. Create a configuration rule to set SSL to Strict, for any hostname containing example.com:

   • When incoming requests match: Custom filter expression

     • Using the Expression Builder:
       Hostname contains "example.com"
     • Using the Expression Editor:
       (http.host contains "example.com")

   • Then the settings are:

     • Setting: SSL
       • Select SSL/TLS encryption mode: Strict

2. Turn off your existing Page Rule and validate the behavior of the configuration rule you created.

3. If your tests succeed, delete the existing Page Rule.