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