title | description | services | author | manager | ms.service | ms.topic | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|
Azure Content Delivery Network from Edgio Premium rules engine features |
Reference documentation for Azure Content Delivery Network from Edgio Premium rules engine features. |
cdn |
duongau |
kumudd |
azure-cdn |
conceptual |
03/20/2024 |
duau |
This article lists detailed descriptions of the available features for Azure Content Delivery Network Rules Engine.
The third part of a rule is the feature. A feature defines the type of action that is applied to the request type that gets identified by a set of match conditions.
The available types of features are:
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 gets applied to a request. |
Token Auth Denial Code | Determines the type of response that gets 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 are case-sensitive. |
Token Auth Parameter | 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 |
---|---|
Bandwidth Parameters | Determines whether bandwidth throttling parameters (for example, ec_rate and ec_prebuf) are active. |
Bandwidth Throttling | Throttles the bandwidth for the response provided by our edge servers. |
Bypass Cache | Determines whether the request can use 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-key gets included or excluded query string parameters associated with a request. A relative path that uniquely identifies an asset for caching. Our edge servers use this relative path when checking for cached content. By default, a cache-key doesn't contain query string parameters. |
Cache-Key Rewrite | Rewrites the cache-key associated with a request. |
Complete Cache Fill | Determines what happens when a request results in a partial cache miss on an edge server. |
Compress File Types | Defines the file formats that get 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 might 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 gets forwarded to the origin server. |
Ignore Origin No-Cache | Determines whether our content delivery network ignores certain directives served from an origin server. |
Ignore Unsatisfiable Ranges | Determines the response that is 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 might 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 is eligible for early revalidation before its time to live (TTL) expires. |
Refresh Zero-Byte Cache Files | Determines how an HTTP client's request for a 0-byte cache asset gets 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 is 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. |
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 |
---|---|
Age Response Header | Determines whether an Age response header is included in the response sent to the requester. |
Debug Cache Response Headers | Determines whether a response might include the X-EC-Debug response header which provides 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. |
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 is assigned to the custom log field in a raw log file. |
Log Query String | Determines whether a query string is stored along with the URL in access logs. |
These features determine whether a request undergoes the optimizations provided by Edge Optimizer.
Name | Purpose |
---|---|
Edge Optimizer | Determines whether Edge Optimizer can be applied to a request. |
Edge Optimizer – Instantiate Configuration | Instantiates or activates the Edge Optimizer configuration associated with a site. |
These features are designed to control how the content delivery network communicates with an origin server.
Name | Purpose |
---|---|
Maximum Keep-Alive Requests | Defines the maximum number of requests for a Keep-Alive connection before it's closed. |
Proxy Special Headers | Defines the set of content delivery network-specific request headers that gets forwarded from an edge server to an origin server. |
These features provide advanced functionality and should get used by advanced users.
Name | Purpose |
---|---|
Cacheable HTTP Methods | Determines the set of extra 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 is informed that our content delivery network service supports QUIC. |
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. |
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. |
For the most recent features, see the Edgio Rules Engine documentation.