Search Results

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

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

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

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 protocol availability is now managed as part of the Host configuration. See Add a Host{target=_blank}.

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

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

Overview This feature lets you modify the client response by manipulating the response received from the origin. You can modify the status code, add, modify, or remove headers. MEL expressions can be used for generating dynamic values for these fields, and to ...

Overview This feature lets you modify the request to the origin by manipulating the request received from the client. You can modify the URI value, add, modify, or remove headers. MEL expressions can be used for generating dynamic values for these fields, and ...

Overview The Origin Error Caching rule lets you set conditions for caching specified error response codes from the origin server. A server error (such as a 5xx server error) typically implies a temporary issue that might persist for a certain duration. You can...

Overview Configure an Origin Selection rule to direct certain client requests (such as requests from a specified user agent) to an alternate origin. This is a Processing Stages rule that is applied to the client request. If you add this rule to a path config...

Overview The Processing Stage rules are applied during a specific stage of the overall transaction (On Client Request, On Origin Request, On Client Response.) Supported Processing Stage rules: - Client Request Access - Sets the conditions for rejecting or redi...

Overview TTL (time-to-live) specifies the amount of time a content item in the CDN cache is considered valid. When the TTL expires, an object is considered stale. Stale content is typically fetched from the origin. However you may decide that under certain con...

Overview By default, TLS versions 1.0, 1.1, 1.2, and 1.3 are enabled. You can configure a TLS Version rule to limit support to specified TLS versions. Configure the Rule Here, we'll describe how to configure the rule with the Delivery Service Management UI. A...

Overview Traffic type is a global setting that must be the same for all site hosts. Supported traffic types are software-downloads, live, or vod. If not explicitly defined, the Traffic Type defaults to software-downloads. Configure the Rule Here, we'll descri...

Introduction 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. The article describes how to add the URL Signing rule to the site configurat...

Overview The X-Forwarded-For header is an HTTP header used to identify the originating IP address of a client (end-user) when a request passes through intermediaries like proxies, load balancers, or CDNs. Without this header, the client's IP address would be h...

Use access control lists (ACLs) to limit access to your site based on a client's IP address, geographic location, autonomous system number (ASN), or use of anonymizer. You can define ACLs at both the host and path levels. Host ACL settings are inherited by pa...