Delivery Domain Configuration
A delivery domain distributes live stream content from CDN edge nodes to end viewers. The delivery domain inherits configuration capabilities from the underlying CDN platform, allowing operators to control how content is accessed, cached, and secured. These settings are configured per delivery domain and apply to all streams served through it.
Common Configuration Areas
Access Control
Access control settings determine which clients and origins are permitted to request content from the delivery domain.
| Setting | Description |
|---|---|
| IP Allowlist / Blocklist | Restrict or deny delivery requests from specific IP addresses or CIDR ranges |
| Referer Control | Allow or block requests based on the HTTP Referer header to prevent hotlinking |
| User-Agent Filtering | Permit or deny requests from specific user agents or clients |
Cache Control
Cache control policies define how CDN edge nodes store and serve stream segments. Proper cache configuration reduces origin load and improves viewer experience.
| Setting | Description |
|---|---|
| Cache TTL | Time-to-live for cached segments at edge nodes |
| Cache Key Rules | Rules that determine which request parameters are included in the cache key |
| Bypass Rules | Conditions under which requests bypass the cache and go directly to the origin |
HTTPS Policies
HTTPS configuration secures content delivery between CDN edge nodes and viewers.
| Setting | Description |
|---|---|
| SSL/TLS Certificate | Upload a custom certificate or use a platform-managed certificate for the delivery domain |
| HTTPS Enforcement | Redirect all HTTP requests to HTTPS or enforce HTTPS-only access |
| TLS Version | Specify the minimum TLS version accepted by the delivery endpoint |
| HSTS | Enable HTTP Strict Transport Security to instruct browsers to use HTTPS exclusively |
Steps
-
Navigate to the Domains page.
In the LLS console, select Domains from the left navigation menu.
-
Open the delivery domain configuration.
Locate the target delivery domain in the Domains list. Click the domain name link. The domain configuration page opens.
-
Complete acceleration-related configurations.
Review and configure each setting category as needed for your deployment:
- Set access control rules to restrict unauthorized playback requests.
- Define cache control policies appropriate for the stream segment duration and latency requirements.
- Upload an SSL/TLS certificate and configure HTTPS enforcement to secure viewer connections.
Save each configuration section after making changes.
Result
Configuration changes are propagated to CDN edge nodes within a few minutes. Updated policies apply to new viewer sessions. Existing sessions may continue under the previous policy until the session is re-established or the edge node refreshes its configuration.
For low-latency streaming deployments, set cache TTLs that align with the segment duration of the HLS playlist (typically 1–2 seconds for LL-HLS). Overly long TTLs can cause viewers to receive stale playlists and experience increased latency.