A featureRules Engine: Defines the type of action that will take place when a set of match conditions have been met. defines the type of action that will be applied to the type of request identified by 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. conditions.
The available types of features are:
These features are designed to control access to content.
Name | Purpose |
---|---|
Determines whether all requests are rejected with a 403 Forbidden response. |
|
Determines whether Token-Based Authentication will be applied to a request. |
|
Determines the type of response that will be returned to a user when a request is denied due to Token-Based Authentication. |
|
Determines whether URL comparisons made by Token-Based Authentication will be case-sensitive. |
|
Determines whether the Token-Based Authentication query string parameter should be renamed. |
These features are designed to customize when and how content is cached.
Name | Purpose |
---|---|
Determines whether bandwidth throttling parameters (i.e., ec_rate and ec_prebuf) will be active. |
|
Throttles the bandwidth for the response provided by our edge servers. |
|
Determines whether the request can leverage our caching technology. |
|
Controls the generation of Cache-Control headers by the edge server when External Max-Age feature is active. |
|
Determines whether the cache-keyA relative path that uniquely identifies an asset for the purpose of caching. Our edge servers use this relative path when checking for cached content and when caching content. By default, a cache-key will not contain query string parameters. will include or exclude query string parameters associated with a request. |
|
Rewrites the cache-key associated with a request. |
|
Determines what happens when a request results in a partial cache miss on an edge server. This feature, which is undergoing end-of-life, has been superseded by the Partial Cache Sharing feature. Please update your rules to use the Partial Cache Sharing feature instead of this one. |
|
Defines the file formats that will be compressed on the server. |
|
Determines the default max-age interval for edge server to origin server cache revalidation. |
|
Controls the generation of Expires headers by an edge server when the External Max-Age feature is active. |
|
Determines the max-age interval for browser to edge server cache revalidation. |
|
Determines the max-age interval for edge server to origin server cache revalidation. |
|
Determines the types of H.264 file formats that may be used to stream content. |
|
Overrides the names assigned to parameters that control seeking through H.264 media when using HTTP Progressive Download. |
|
Determines whether an HTTP client's no-cache requests will be forwarded to the origin server. |
|
Determines whether our CDN will ignore certain directives served from an origin server. |
|
Determines the response that will be returned to clients when a request generates a 416 Requested Range Not Satisfiable status code. |
|
Controls how long past the normal expiration time a cached asset may be served from an edge server when the edge server is unable to revalidate the cached asset with the origin server. |
|
Determines whether a request can generate partially cached content. |
|
Determines whether cached content will be eligible for early revalidation before its TTL expires. |
|
Determines how an HTTP client's request for a 0-byte cache asset is handled by our edge servers. |
|
Defines the set of status codes that can result in cached content. |
|
Determines whether expired cached content will be delivered when an error occurs during cache revalidation or when retrieving the requested content from the customer origin server. |
|
Improves performance by allowing our edge servers to serve stale client to the requester while revalidation takes place. |
The Comment feature allows a note to be added within a rule.
These features are designed to add, modify, or delete headers from the request or response.
Name | Purpose |
---|---|
Determines whether an Age response header will be included in the response sent to the requester. |
|
Determines whether a response may include debug cache response headers which provide information on the cache policy for the requested asset. |
|
Overwrites, appends, or deletes a header from a request. |
|
Overwrites, appends, or deletes a header from a response. |
|
Allows the IP address of the requesting client to be added to the request as a custom request header. |
These features are designed to customize the data stored in raw log files.
Name | Purpose |
---|---|
Determines the format and the content that will be assigned to the custom log field in a raw log file. |
|
Determines whether a query string will be stored along with the URL in access logs. |
|
Determines whether a client's IP address will be masked for logging and reporting purposes. |
These features determine whether a request will undergo the optimizations provided by Edge Optimizer.
Name | Purpose |
---|---|
Determines whether Edge Optimizer can be applied to a request. |
|
Instantiates or activates the Edge Optimizer configuration associated with a site. |
These features are designed to control how the CDN communicates with an origin server.
Name | Purpose |
---|---|
Defines the maximum number of requests for a Keep-Alive connection before it is closed. |
|
Defines the set of CDN-specific request headers that will be forwarded from an edge server to an origin server. |
These features provide advanced functionality that should only be used by advanced users.
Name | Purpose |
---|---|
Determines the set of additional HTTP methods that can be cached on our network. |
|
Defines the threshold for determining whether a POST response can be cached. |
|
Determines whether the client will be informed that our CDN service supports QUIC. |
|
Determines whether our service will attempt revalidation with your origin server when communication has been temporarily disabled due to repeated origin server availability issues. |
|
Determines how often the system will attempt to connect to an unavailable origin server. |
|
Tunes your caching configuration to optimize performance for live streams and to reduce the load on the origin server. |
|
Assigns a value to a user-defined variable that is passed to your bespoke traffic processing solution. |
These features allow a request to be redirected or rewritten to a different URL.
Name | Purpose |
---|---|
Determines whether requests can be redirected to the hostname defined in the Location header returned by a customer origin server. |
|
Redirects requests via the Location header. |
|
Rewrites the request URL. |
The Web Application Firewall feature determines whether a request will be screened by Web Application Firewall (Legacy).