Features

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 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:

Access
Caching
Comment
Headers
Logs
Origin
Specialty
URL

Access

These features are designed to control access to content.

Name	Purpose
Deny Access (403)	Determines whether all requests are rejected with a 403 Forbidden response.
Token Auth	Determines whether Token-Based Authentication will be applied to a request.
Token Auth Denial Code	Determines the type of response that will be returned to a user when a request is denied due to Token-Based Authentication.
Token Auth Ignore URL Case	Determines whether URL comparisons made by Token-Based Authentication will be case-sensitive.
Token Auth Parameter	Determines whether the Token-Based Authentication query string parameter should be renamed.

Caching

These features are designed to customize when and how content is cached.

Name	Purpose
Bandwidth Parameters	Determines whether bandwidth throttling parameters (i.e., ec_rate and ec_prebuf) will be active.
Bandwidth Throttling	Throttles the bandwidth for the response provided by our edge servers.
Bypass Cache	Determines whether the request can leverage our caching technology.
Cache-Control Header Treatment	Controls the generation of Cache-Control headers by the edge server when External Max-Age feature is active.
Cache-Key Query String	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.
Cache-Key Rewrite	Rewrites the cache-key associated with a request.
Complete Cache Fill (EOL)	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.
Compress File Types	Defines the file formats that will be compressed on the server.
Default Internal Max-Age	Determines the default max-age interval for edge server to origin server cache revalidation.
Expires Header Treatment	Controls the generation of Expires headers by an edge server when the External Max-Age feature is active.
External Max-Age	Determines the max-age interval for browser to edge server cache revalidation.
Force Internal Max-Age	Determines the max-age interval for edge server to origin server cache revalidation.
H.264 Support (HTTP Progressive Download)	Determines the types of H.264 file formats that may be used to stream content.
H.264 Support Video Seek Params	Overrides the names assigned to parameters that control seeking through H.264 media when using HTTP Progressive Download.
Honor No-Cache Request	Determines whether an HTTP client's no-cache requests will be forwarded to the origin server.
Ignore Origin No-Cache	Determines whether our CDN will ignore certain directives served from an origin server.
Ignore Unsatisfiable Ranges	Determines the response that will be returned to clients when a request generates a 416 Requested Range Not Satisfiable status code.
Internal Max-Stale	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.
Partial Cache Sharing	Determines whether a request can generate partially cached content.
Prevalidate Cached Content	Determines whether cached content will be eligible for early revalidation before its TTL expires.
Refresh Zero-Byte Cache Files	Determines how an HTTP client's request for a 0-byte cache asset is handled by our edge servers.
Set Cacheable Status Codes	Defines the set of status codes that can result in cached content.
Stale Content Delivery on Error	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.
Stale While Revalidate	Improves performance by allowing our edge servers to serve stale client to the requester while revalidation takes place.

Comment

The Comment feature allows a note to be added within a rule.

Headers

These features are designed to add, modify, or delete headers from the request or response.

Name	Purpose
Age Response Header	Determines whether an Age response header will be included in the response sent to the requester.
Debug Cache Response Headers	Determines whether a response may include debug cache response headers which provide information on the cache policy for the requested asset.
Modify Client Request Header	Overwrites, appends, or deletes a header from a request.
Modify Client Response Header	Overwrites, appends, or deletes a header from a response.
Set Client IP Custom Header	Allows the IP address of the requesting client to be added to the request as a custom request header.

Logs

These features are designed to customize the data stored in raw log files.

Name	Purpose
Custom Log Field 1	Determines the format and the content that will be assigned to the custom log field in a raw log file.
Log Query String	Determines whether a query string will be stored along with the URL in access logs.
Mask Client Subnet	Determines whether a client's IP address will be masked for logging and reporting purposes.

Origin

These features are designed to control how the CDN communicates with an origin server.

Name	Purpose
Maximum Keep-Alive Requests	Defines the maximum number of requests for a Keep-Alive connection before it is closed.
Proxy Special Headers	Defines the set of CDN-specific request headers that will be forwarded from an edge server to an origin server.

Specialty

These features provide advanced functionality that should only be used by advanced users.

Name	Purpose
Cacheable HTTP Methods	Determines the set of additional HTTP methods that can be cached on our network.
Cacheable Request Body Size	Defines the threshold for determining whether a POST response can be cached.
QUIC	Determines whether the client will be informed that our CDN service supports QUIC.
Revalidate While Stale	Determines whether our service will attempt revalidation with your origin server when communication has been temporarily disabled due to repeated origin server availability issues.
Revalidate While Stale Timer	Determines how often the system will attempt to connect to an unavailable origin server.
Streaming Optimization	Tunes your caching configuration to optimize performance for live streams and to reduce the load on the origin server.
User Variable	Assigns a value to a user-defined variable that is passed to your bespoke traffic processing solution.

URL

These features allow a request to be redirected or rewritten to a different URL.

Name	Purpose
Follow Redirects	Determines whether requests can be redirected to the hostname defined in the Location header returned by a customer origin server.
URL Redirect	Redirects requests via the Location header.
URL Rewrite	Rewrites the request URL.