- Home
- /Workers
- /Configuration
- /Page Rules
Page Rules
Last updated Apr 23, 2026|Copy as Markdown|View as Markdown|Agent setup OverviewPage Rules with WorkersAffected Page RulesAlways Use HTTPSAutomatic HTTPS RewritesBrowser Cache TTLBrowser Integrity CheckCache Deception ArmorCache LevelDisable ZarazEdge Cache TTLEmail ObfuscationForwarding URLIP Geolocation HeaderOrigin Cache ControlRocket LoaderSecurity LevelSSL
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 Page Rules to learn more about configuring Page Rules.
Cloudflare acts as a reverse proxy 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 global network acts as your origin server and responds to requests directly from the Cloudflare global network.
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 evaluates and disabled 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.
- Worker makes a same-zone or other-zone subrequest. Because this is a Worker route, Cloudflare disables a number of features, including some that would be set by Page Rules.
Page Rules are evaluated both at the client-to-Worker request stage (step 2) and the Worker subrequest stage (step 5).
If you are experiencing Page Rule errors when running Workers, contact your Cloudflare account team or Cloudflare Support.
The following Page Rules may not work as expected when an incoming request is matched to a Worker route:
This is because the default setting of these Page Rules will be disabled when Cloudflare recognizes that the request is headed to a Worker.
Testing
Due to ongoing changes to the Workers runtime, detailed documentation on how these rules will be affected are updated following testing.
To learn what these Page Rules do, refer to Page Rules.
Same zone versus other zone
A same zone subrequest is a request the Worker makes to an orange-clouded hostname in the same zone the Worker runs on. Depending on your DNS configuration, any request that falls outside that definition may be considered an other zone request by the Cloudflare network.
PreviousMultipart upload metadataNextPlacement