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 to learn more about configuring Page Rules.
Page Rules with Workers
Cloudflare acts as a 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 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.
- Request arrives at Cloudflare data center.
- Cloudflare decides if this request is a Worker route.
- Because this is a Worker route, Cloudflare disables a number of features, including some that would be set by Page Rules.
- Page Rules run as part of normal request processing with some features now disabled.
- Worker executes.
Disabled Page Rules
The following Page Rules are disabled 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
- Rocket Loader
When implementing the Email Obfuscation Page Rule be aware that Email Obfuscation will run on subrequests, but not on parent requests. If the subrequest is going to an external site and the subrequest URL does not match the Page Rule URL configured for your site, the Email Obfuscation Page Rule will not execute.
For example, if the subrequest is going to an external object storage bucket with the URL being something like
yoursite.cloudprovider.com, which does not match the Page Rule configured for your site, the Email Obfuscation Page Rule will be skipped.