Applying Actions to Requests

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.

The set of actions that will be applied to a particular type of request may be defined by simply adding one or more features to the conditional statement that identifies the desired request type.

Learn more about setting up match conditions.

Features are organized by category. A brief description for each category is provided below.

Category	Description
General	This category contains the Comment feature which allows notes to be added to a rule.
Caching	This category may be used to define caching, compression, and bandwidth throttling policies. The most common usage for this type of feature is to determine whether content will be cached and for how long.
Logs	This category may be used to define the type of data that is stored in a raw log file. This category is intended only for accounts on which raw log file support has been activated and raw log file archival has been enabled. Please contact your CDN account manager to find out more information on raw log file activation.
Access	This category may be used to define access control (e.g., deny access to content or secure it via Token-Based Authentication).
Headers	This category may be used to define request and response header behavior (e.g., set or delete header data).
Specialty	This category may be used to define advanced actions through which a custom configuration for a specialized need may be achieved.
Origin	This category may be used to define the instructions provided by an edge server to an origin server.
URL	This category may be used to redirect and rewrite request URLs.