Skip to content

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 Page Rules to learn more about configuring Page Rules.

Page Rules with Workers

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.

  1. Request arrives at Cloudflare data center.
  2. 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.
  3. Page Rules run as part of normal request processing with some features now disabled.
  4. Worker executes.
  5. 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.

Affected Page Rules

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.

To learn what these Page Rules do, refer to Page Rules.

Always Use HTTPS

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Ignored
WorkerOther ZoneRule Ignored

Automatic HTTPS Rewrites

SourceTargetBehavior
ClientWorkerRule Ignored
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Browser Cache TTL

SourceTargetBehavior
ClientWorkerRule Ignored
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Browser Integrity Check

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Ignored
WorkerOther ZoneRule Ignored

Cache Deception Armor

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Cache Level

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Disable Zaraz

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Edge Cache TTL

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Email Obfuscation

SourceTargetBehavior
ClientWorkerRule Ignored
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Forwarding URL

SourceTargetBehavior
ClientWorkerRule Ignored
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

IP Geolocation Header

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Origin Cache Control

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored

Rocket Loader

SourceTargetBehavior
ClientWorkerRule Ignored
WorkerSame ZoneRule Ignored
WorkerOther ZoneRule Ignored

Security Level

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Ignored
WorkerOther ZoneRule Ignored

SSL

SourceTargetBehavior
ClientWorkerRule Respected
WorkerSame ZoneRule Respected
WorkerOther ZoneRule Ignored