ナビ付きでトピックを開く

 

Custom Request Handling via Rules Engine

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.
Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior.

Purpose: Rules Engine is designed to be the final authority on how specific types of requests are processed by the CDN.

ClosedLearn more.

The MCC 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 MCC configuration, the default behavior of our edge servers, and even the instructions provided by an origin server.

Common Uses:

Although Rules Engine is supported on all HTTP-based platforms (i.e., HTTP Large, HTTP Small, and ADN), each configuration is specific to a single platform. For example, a policyRules Engine: Refers to a read-only version of a set of rules that identify requests and the set of actions that can be applied to them. A policy may be applied to either the Staging or Production environment. created for the HTTP Large platform will not affect how requests to the HTTP Small platform are handled and vice-versa.

Getting Started

Setting up Rules Engine involves the following steps:

  1. Create a draft that identifies the type of requests to which a set of actions will be applied.
  2. Once the draft has been finalized, convert it into a policy by locking it.
  3. Optional. Test the configuration by deploying the policy to the Staging environment.
  4. Apply the configuration to live traffic by deploying the policy to the Production environment.

View setup workflow.

More Information