Page Rules

Page Rules trigger certain actions whenever a request matches one of the URL patterns you define. You can define a page rule to trigger one or more actions whenever a certain URL pattern is matched. Refer to the Page Rules Support article Open external link to learn more about configuring Page Rules.

​​ Page Rules with Workers

Cloudflare acts as a reverse proxy Open external link to provide services, like Page Rules, to Internet properties. Your application’s traffic will pass through a Cloudflare data center that is closest to the visitor. There are hundreds of these around the world, each of which are capable of running services like Workers and Page Rules. If your application is built on Workers and/or Pages, the Cloudflare network edge Open external link acts as your origin server and responds to requests directly from the Cloudflare edge.

When using Page Rules with Workers, the following workflow is applied.

1. Request arrives at Cloudflare data center.
2. Cloudflare decides if this request is a Worker route.
3. Because this is a Worker route, Cloudflare disables a number of features, including some that would be set by Page Rules.
4. Page Rules run as part of normal request processing with some features now disabled.
5. Worker executes.

If you are experiencing Page Rule errors when running Workers, contact your Cloudflare account team or Cloudflare Support Open external link .

​​ Disabled Page Rules

The following Page Rules may not work as expected when an incoming request is matched to a Worker route:

• Always Online
• Always Use HTTPS
• Auto Minify
• Automatic HTTPS Rewrites
• Disable Apps
• Email Obfuscation
• Forwarding URL
• Host Header Override
• Mirage
• Rocket Loader

This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.

To learn what these Page Rules do, refer to Understanding and configuring Cloudflare Page Rules Open external link .

​​ Email Obfuscation