Rule

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.

A draft provides the framework through which one or more rules may be created. Each rule provides instructions on how requests will be handled by the CDN. It does this by identifying specific types of requests (i.e., match) and the set of actions (i.e., features) that will applied to them.

One or more rules may be administered from within a single draft.

A rule consists of:

A set of conditional expressionRules Engine: Refers to the logic (i.e., IF and ELSE IF) through which one or more match conditions identify a type of request.s that define the logic through which requests are identified.
A set of matchRules Engine: Defines a prerequisite that must be met before one or more actions (i.e., features) may be applied to a request.es that define a request type.
A set of featureRules Engine: Defines the type of action that will take place when a set of match conditions have been met.s that define how the CDN will handle the above requests.

These elements are highlighted in the following illustration.

Rule

More Information