Show search and navigation.
Rules Engine allows the customization of requests handled by our CDN. Sample customizations that may be performed are:
The steps required to set up a custom configuration are indicated in blue in the following illustration.
A draft of a policy consists of one or more rules meant to identify requests (i.e., match conditions) and the set of actions (i.e., features) that will be applied to them. A draft is a work in progress that allows frequent configuration updates without impacting site traffic. Once a draft is ready to be finalized, it should be converted into a read-only policy.
A policy is the finalized version of a draft. It is read-only and it may be applied to staging or production traffic.
Submitting a deploy request will trigger an automated review for the corresponding policy. If the policy is approved, then it may take up to 1 hour to apply a newly approved policy to the Production environment. Deployment to the Staging environment should only take approximately 15 minutes.
Complex policies that require manual review typically require approximately 4 business hours for approval.
Rules Engine is licensed through rule groups. Each rule group defines the set of matches and features that will be available on your account.
The recommended procedure for updating your Rules Engine configuration is described below.
Create a duplicate copy of the policy that is currently deployed to the Production environment.
Deploy the desired policy to the Staging environment.
Verify that the policy works as intended by submitting requests to the Staging environment.
Deploy the desired policy to the Production environment.
Rules Engine was not designed to be completely turned off, since the business case to do so is quite rare. However, the procedure described below will replicate this behavior.
It should look similar to the following illustration:
Deploy the policy to the Production or Staging environment.
A rule identifies a type of request and how it will be handled by our CDN.
It consists of the following components:
Yes. A request is processed by all rules in the order in which they are listed. This allows multiple customized actions to be applied to the request. If multiple rules with conflicting instructions are applicable to the request in question, then the last rule to be processed will take precedence.
The match or feature in question may belong to an Rules Engine group that has not been enabled on your account. Please contact your CDN account manager for more information.
A Deploy Request applies a policy to either the Staging or Production environment. If a policy was previously deployed to that environment, then it will be overwritten.
The use of Deploy Requests serves various purposes:
It allows a policy to be applied to an environment as needed.
A policy may be reused as needed.
For example, an event (e.g., sale or holiday) may require a special configuration. An event-specific policy may be applied during the event. Once the event is over, the old policy may be reapplied.
It tracks the progress of a request to apply a policy to an environment.
This historical information provides context as to when and why a policy was deployed to an environment.
A Deploy Request cannot be submitted under the following conditions:
Another policy is still being deployed to that environment. Please wait until the previous Deploy Request enters one of the following states:
No. The Staging environment is designed for functional testing and is of a much smaller scale than the Production CDN environment.
Please keep traffic below the following levels:
Submit a standard purge request.
Purges are applied to both the Staging and the Production environment.
Rules Engine may occasionally report one of the following errors:
'Match' match is no longer available
'Feature' feature is no longer available
This error typically occurs due to one of the following factors:
Browser Cache: Try performing a force refresh (aka hard refresh) to load the page without cache.
Force Refresh on Windows:
Hard refresh on macOS:
Platform Restrictions: Check whether the match or feature is supported on the desired delivery platform.