HLS feature User Guide [EN]
Enabling HLS support
To enable the HLS support feature for your CDN resource in the user panel, within the Anycast CDN section, open your particular CDN resource, navigate to the Locations tab, and scroll down to the Functional features block, as shown below.
By default, the feature is turned off. To enable HLS support, switch the toggle into the active position as shown below.
Configuring HLS support
TTL for playlists
Configuration determines how long playlist files (manifests) will be cached before checking the origin for updates and custom TTLs for various HTTP status codes.
Extensions
The default .m3u8 (text-based playlist) extension is the standard UTF-8-encoded format used by HLS to list media segments and stream variants.
CDN cache control
When content is requested, the CDN retrieves it from the origin server and caches a copy. Cached files remain in the CDN as long as they are in demand, following the configured caching policies.
Active TTL (Update Time To Live)
Time until file refresh. When the TTL expires, the file is re-cached from the origin. If unchanged, only headers update.
Default value is 10 seconds; maximum value is 365 days.
Custom Active TTL for different HTTP codes
This feature allows you to set different cache durations depending on the HTTP status codes. For example, 200 OK responses can have a longer TTL, while errors like 404 can refresh more often to ensure accuracy.
To configure custom TTL codes for different HTTP responses, click on the code you need to add, or use the dedicated button below to add your error code and TTL.
With the toggle, you can apply a default 10-second TTL, enter a 10-second TTL, or switch it off and input your own value.
Honor response TTL headers
If you send an X-Accel-Expires, Expires, or Cache-Control header with your files, it will override the defined TTL.
Browser Active TTL
The same as Active TTL, but for browser cache; the CDN just returns headers, and the browser maintains its own cache by following these headers.
Default value is 2 days; maximum value is 365 days.
Min requests to cache
Define here the minimum number of file requests before it is cached.
The default value is 1 request
TTL for chunks
Configuration determines how long media chunks (segments) will be cached before revalidation with the origin and TTLs for various HTTP status codes.
Extensions
Both .ts and .m4s chunk extensions are the standard media segment container formats used by HLS to carry the encoded audio/video data referenced in the playlist.
.tsuses MPEG-2 Transport Stream for self-contained sequential segments..m4suses fragmented MP4 (fMP4) with initialization and media fragments.
At least one format must be selected here.
Mode
In Common mode, configurations of your pull zone will be applied to the settings below and won’t be editable.
In Specific mode, you can configure every cache control parameter in detail.
Select the Specific mode to configure a particular TTL for any HTTP status codes (pre-set or custom). Use common mode to apply a single default TTL for all responses. Use the toggle to switch between modes.
Please note: switching back to common mode from specific mode will reset your TTL configuration.
CDN cache control
When content is requested, the CDN retrieves it from the origin server and caches a copy. Cached files remain in the CDN as long as there is demand for them, following the configured caching policies.
Active TTL (Update Time To Live)
Time until file refresh. When the TTL expires, the file is re-cached from the origin. If unchanged, only headers update.
Default value is 2 days; maximum value is 365 days.
Custom Active TTL for different HTTP codes
This feature lets you set varied cache durations based on HTTP status codes. For example, 200 OK responses can have a longer TTL, while errors like 404 can refresh more often to ensure accuracy.
To configure custom TTL codes for different HTTP responses, click on the code you need to add, or use the dedicated button below to add your error code and TTL.
Honor response TTL headers
If you send an X-Accel-Expires, Expires, or Cache-Control header with your files, it will override the defined TTL.
Browser Active TTL
The same as Active TTL, but for browser cache; the CDN just returns headers, and the browser maintains its own cache by following these headers.
Default value is 2 days; maximum value is 365 days.
Min requests to cache
Define here the minimum number of file requests before it is cached.
The default value is 1 request
When you finish the necessary setup, click Save Changes before leaving the page.