Delivery - Video CDN [EN]

The CDN intelligently distributes content across its points of presence (PoPs) based on file popularity within specific regions. For each region (which, in our terminology, corresponds to a PoP), the system tracks individual file demand and calculates popularity independently.

Once a file is requested and loaded into the system, the CDN begins delivering traffic to it using multiple performance metrics.

This evaluation is continuous: the system reassesses delivery paths in real time based on changing demand, network conditions, and cache state. As a result, the same user may receive a file from one PoP at a given time and be routed to another PoP for the same file just minutes later.

This adaptive approach ensures that files are always served from the most relevant and responsive location, improving performance and optimizing overall resource usage. Each PoP independently tracks requests to files, improving the distribution strategies.

HTTP-based delivery

All content delivery within the system is built on the HTTP protocol: HTTP, HTTPS, and HTTP/2. This applies to both adaptive streaming (such as HLS and DASH) and direct file downloads.

Protocols outside the HTTP family (like RTMP or RTSP) are not supported at this time.

The HTTP/3 protocol is not supported yet but might be added in the future.

Querying

A significant part of the available features is built-in, enabled by design, and does not require explicit configuration via the control panel.

To leverage these features, you should construct the URL in accordance with the expected format and include the appropriate parameters. A complete reference of supported URL parameters can be found on Url parameters reference.

Accepted Delimiters and Compatibility Notes

When encoding parameters directly into the URL path, two delimiter styles are supported for separating parameter names and values: the equals sign = and the underscore _.

Mixing delimiters within the same URL is not supported. Only one style may be used per URL.

Example of a valid underscore-style URL:

Alternative valid format using equals:

Although the = character is part of the sub-delims set as per RFC 3986 §2.2, its use within URL paths (especially outside of query strings) can lead to inconsistent behavior in some User-Agents (UA), such as embedded players or intermediate caching devices.

Therefore, it is recommended to prefer the underscore _ format for better compatibility, especially in environments where strict parsing rules or non-browser clients are involved. The = style remains technically valid and supported by the backend but should be used with caution due to potential interoperability issues.

Disable certain url parameters

You can disable certain url parameters overriding at the account or domain level. This may be needed for security reasons (especially when Url Signature is disabled).

Here is a list of such parameters: buffer, download2, download3, initial buffer, ip, media, referrer, secure cookie, speed.

See also

How to disable url parameters overriding

Guide for configuring the feature

Manipulating the delivery algorithm

In typical scenarios, the CDN selects the optimal delivery point based on the IP address of the requester — usually the end user’s browser. However, if a user retrieves CDN content from their own backend or another server instead of directly from the visitor’s IP, the CDN will make routing decisions based on the server’s IP. This often leads to suboptimal performance, as the request origin does not reflect the actual location of the end user.

To address this, the ip parameter can be used to explicitly pass the real client IP. This allows the CDN to make accurate routing decisions and direct the traffic to the most appropriate edge node, based on the user’s actual location.

While this approach goes against best practices (particularly the general recommendation to avoid CDN-over-CDN setups), it can be useful in specific edge cases. For instance, if the client must deliver a manifest file to the browser through a custom or private mechanism, they can prefetch the manifest from the CDN using the ip parameter to ensure it’s selected from the correct region.

This helps mitigate misrouting and ensures optimal delivery when direct browser access isn’t possible.

See also

“ip” parameter

Url parameter, that overrides the visitor’s IP address at traffic routing

Delivery Rate Management

To optimize bandwidth usage, the CDN can deliver large files (including video content) at a controlled rate that aligns with the actual consumption speed on the client side, rather than pushing the entire file as quickly as possible. This acts as a kind of bandwidth overusage protection.

The technique, often referred to as throttled or rate-matched delivery, ensures that data is transferred progressively — just fast enough to support continuous playback or sequential file consumption, without unnecessary buffering or overfetching.

By reducing the amount of excess data transferred, this feature helps reduce overall traffic volume. This can result in significant cost savings, especially for platforms handling heavy media files, or long-form video content. Delivering only what’s needed, when it’s needed, provides a balance between user experience and efficient resource consumption.

Rate management is applicable to file-based delivery only. Streaming segments are not applicable to the rate.

See also

How to manage delivery rate

Guide for changing content handling behavior in browsers

How to manage delivery rate of video files

Guide for changing content handling behavior in browsers

“speed” parameter

Url parameter, that defines delivery rate per url

Content Handling in Browsers

You can control how the browser handles downloadable files using HTTP headers.

By default, if you set up a web server, upload a media file, and click the link, your browser will likely just demonstrate it (especially if it’s an .mp4).

But what if you want the browser to say, “Hey, would you like to download this instead?” — that’s where Content-Disposition headers come in.

This feature allows you to trigger download behavior by setting a specific parameter. You can even define the filename that the browser should suggest to the user. If no filename is provided, the original filename will be used instead.

See also

How to make browser download the video

Guide for changing content handling behavior in browsers

“download2” parameter

Url parameter, that overrides content handling parameters

IPv6