Skip to main content
Advanced Search
Search Terms
Content Type

Exact Matches
Tag Searches
Date Options
Updated after
Updated before
Created after
Created before

Search Results

218 total results found

Rule Configuration / Supported Rules

Media Delivery

Bypass cache

Media Delivery Rule Configuration / Supported Rules

Overview A Bypass Cache rule instructs the CDN to always fetch the content from the origin server. For example, if your use case relies on real-time data or if you frequently update a particular content item and you want the latest version to be fetched from ...

Z cache key management

Media Delivery Rule Configuration / Supported Rules

Overview The CDN assigns a unique identifier (a cache key) to each object in the CDN cache. The cache key is generated from the URI of the content request. Use the Cache Key Management rule to customize cache key generation. Configure a basic Cache Key Manag...

Cache time to live

Media Delivery Rule Configuration / Supported Rules

Overview The Cache Time to Live (TTL) rule lets you set caching policies to determine how long content is cached on the CDN before it is considered stale. The rule can also be configured to influence caching behavior on the client cache. Configuring Client TTL...

Client byte range request

Media Delivery Rule Configuration / Supported Rules

Overview The Client Byte Range Request rule allows for enabling or disabling client byte range requests for a particular host or path. Range request support is enabled by default. When Client Byte Range Request is disabled, the “Content-Range” header in client...

Client ipv6 support

Media Delivery Rule Configuration / Supported Rules

Overview The Client IPv6 Support rule lets you enable or disable IPv6 support for all site hosts. By default, client IPv6 support is enabled. Enabled: The CDN responds to DNS queries with an AAAA record, allowing IPv6-capable clients to connect over IPv6. ...

Client request access

Media Delivery Rule Configuration / Supported Rules

Overview This feature lets you set the conditions for rejecting or redirecting client requests based on header information. For example, to block referrer URLs or user agents. This is a Processing Stages rule that is applied to the client request. It can be c...

Cmcd old self service rule

Media Delivery Rule Configuration / Supported Rules

29.8 Demo - said we decided to enable it by default, so there will no longer be a toggle button in the UI. If the input includes headers that trigger CMCD, then they will. But Noam P. says they might want to have control to disable it. The headers in the requ...

Compression 1

Media Delivery Rule Configuration / Supported Rules

Overview The Compression rule enables Brotly/GZip compression at the edge. The compression selection method is determined by the client's Accept-Encoding header. Configure the Rule Here, we'll describe how to configure the rule with the Delivery Service Manage...

Cors headers

Media Delivery Rule Configuration / Supported Rules

Overview Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows a server to specify origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. This is useful when a site resource needs...

Debug info rule

Media Delivery Rule Configuration / Supported Rules

Overview Use this feature to include helpful debugging information in the client response -- but only when it's explicitly requested. When a client request includes the specified header (name and value), the server adds debug information to the response in the...

Discovery url signing

Media Delivery Rule Configuration / Supported Rules

As a content publisher, you can use Qwilt URL Signing for authorization, to safeguard against unauthorized access to your content that is delivered through the Qwilt CDN. This article describes how to configure the Discovery URL Signing rule, a custom rule de...

Http keep alive internal

Media Delivery Rule Configuration / Supported Rules

WIP. This is an internal draft. When Max Number of Requests per Connection is supported, merge the relevant info back from this topic into the published topic. Overview Use the HTTP Keep Alive rule to manage persistent client-to-CDN connections for faster con...

Hhttp keep alive

Media Delivery Rule Configuration / Supported Rules

Overview Use the HTTP Keep Alive rule to manage persistent client-to-CDN connections for faster content delivery, reduced latency, and improved performance. This rule may be configured at the host level, but not at the path level. Connection pooling and connec...

Http methods 1

Media Delivery Rule Configuration / Supported Rules

Overview The HTTP Methods rule sets the HTTP methods available to clients, to enable a client payload, and to set the maximum payload size (in bytes). Configure the Rule Here, we'll describe how to configure the rule with the Delivery Service Management UI. ...

Http protocols 1

Media Delivery Rule Configuration / Supported Rules

HTTP protocol availability is now managed as part of the Host configuration. See Add a Host{target=_blank}.

Http to https redirect 1

Media Delivery Rule Configuration / Supported Rules

Overview If you want to block your site from being accessed over HTTP, you can configure an HTTP to HTTPS Redirect rule to force the CDN to redirect HTTP requests to HTTPs. The rule configuration also sets the response code. Configure the Rule Here, we'll desc...

Low latency live

Media Delivery Rule Configuration / Supported Rules

Overview Use the Low Latency Live rule to enable advanced features for the optimized delivery of Low Latency DASH and/or HLS streams. This rule is available for sites configured for the Live traffic type. :::(Warning) (Warning:) The Low Latency Live rule is de...