Purpose: Rules Engine is designed to be the final authority on how specific types of requests are processed by the CDN.
Learn more.
The TCC contains a variety of settings that may be leveraged to configure how content is delivered through the CDN. However, your unique working environment may require an additional level of customization. For this reason, we provide an interface through which you can create custom policies that will override your TCC configuration, the default behavior of our edge servers, and even the instructions provided by an origin server.
Common Uses:
- Override or define a custom cache policy.
-
Secure or deny requests for sensitive content.
-
Redirect requests.
-
Store custom log data.
Getting Started
Setting up Rules Engine involves the following steps:
- Create a draft that identifies the type of requests to which a set of actions will be applied.
- Once the draft has been finalized, convert it into a policy by locking it.
- Optional. Test the configuration by deploying the policy to the Staging environment.
- Apply the configuration to live traffic by deploying the policy to the Production environment.
More Information
- Changes Introduced with the Rules Engine Upgrade
- Frequently Asked Questions - Rules Engine
- Customizing Request Handling via Rules Engine Tutorial
- Policy
- Deploy Request
- Environment
Edgecast CDN