Large File Delivery Optimization is designed for CDN resources that serve files larger than 10 MB. When enabled, Orange's CDN requests content from the origin in 10 MB chunks using HTTP range requests, caches each chunk independently, and assembles the response from the cached portions.
A range request includes the Range HTTP header to indicate the byte or part of the content to be returned. If the request has a Range: bytes=123537047-123545047 header, the CDN requests a 10 MB chunk (10,485,760 bytes, range 115343360-125829119) from the origin, caches this chunk, and serves the requested range (123537047-123545047) to the end user.
For this option to work, the origin server must support range requests.
Configuration guidelines
Large File Delivery Optimization is set in Resource settings in the steps below. A rule can apply it to one path. Review these requirements and recommendations before configuring the option:
The origin server must support HTTP Range Requests.
The Content-Length and Etag headers must be consistent across the origin.
When enabled in Resource settings, the option applies to all content in the CDN resource, which can increase the load on the origin. Consider activating Origin Shielding before enabling this feature, or enable it during off-peak hours.
Remember to purge the cache after enabling Large File Delivery Optimization.
Large File Delivery Optimization is generally unnecessary for HLS and MPEG-DASH because these formats already split media into small segments that are cached independently.
Configuration steps
To enable Large File Delivery Optimization via the CDB Technical Web Portal:
2. Click the CNAME of the required CDN resource to open Resource settings.
3. Navigate to the OPTIONS tab.
4. In the left menu, click Content to scroll to the Content section.
5. Enable the Large files delivery optimization toggle.
6. Click Save changes.
⚠️
When Large files delivery optimization is enabled, the HTTP Etag header is concealed in responses.
A file larger than 10 MB keeps the origin busy when Orange's CDN fetches it in one piece. Slice fetches that file in parts no larger than 10 MB, caches each part, and sends the viewer the first bytes without waiting for the whole file. The origin must support HTTP range requests and send a consistent Content-Length and Etag. Responses conceal the HTTP Etag header. Purge the cache after turning slice on.
Orange's CDN requests each large file from the origin in parts of up to 10 MB. The origin must accept HTTP range requests.
enabled and value are required. Setting both to true turns slice on. The JSON field is slice; the key Slice is ignored. A request that also enables gzipOn, brotli_compression, or fetch_compressed returns HTTP 400.
Large files delivery optimization fetches a file larger than 10 MB from the origin in parts no larger than 10 MB, caches each part, and returns the requested bytes without waiting for the whole file. The origin must support HTTP range requests and send a consistent Content-Length and Etag. Responses conceal the HTTP Etag header. Purge the cache after turning slice on. Declare the option with the Terraform provider v2.
A new resource without slice leaves the option unset. After the option is saved, keep the object in the configuration. Setting slice to null, or removing the options block, leaves the saved enabled and value in place. A REST API call removes the option by sending JSON null.
Slice cannot be enabled in the same configuration as gzip, Brotli, or fetch compressed. Each pairing returns HTTP 400, and the error names those two options.
Turn slice on
Set enabled and value to true. Both fields are required. After terraform apply, Orange's CDN fetches files larger than 10 MB in parts no larger than 10 MB and caches each part. On the resource, the option applies to every file.