HLS streaming through a CDN Static service

Introduction

We recommend to use CDN HTTP Live service as it is based on CDN Static service and it is tailored for HLS streaming.

However HLS and other HTTP live streams can be delivered via CDN Static services and HLS and other HTTP on-demand streams can be delivered via CDN Static or CDN Static Push services.

Integration on your end

The following is recommended for .m3u8 files.

Live streaming

On your end you need a streaming server configured to HTTP streaming. For smooth playing it is recommended to set max-age (value of the Cache-Control HTTP header on your origin server) for your video segments (usually with .ts extension) to be around their length (usually 10 seconds).

Integration on CDN end

Let's assume that your HLS stream is located on the following origin URL.

https://mycompany.com/stream/playlist.m3u8

Create a CDN Static service with Origin Domain to mycompany.com.

Let's assume that cdn.mycompany.com is the Service Domain of your new CDN Static service. Then your CDN accelerated HLS stream is located on the following CDN URL.

https://cdn.mycompany.com/stream/playlist.m3u8

Integration of CDN Static Push service is analogical. First create a CDN Storage and upload your HLS on-demand stream to it. Then use that CDN Storage as Origin Storage for your CDN Static Push service.

HLS optimization

Internally we can optimize CDN Static and CDN Static Push services for HTTP streaming (HLS, Dash, etc.). Please contact us below to request this optimization.

What next?

Read about the following topics.

Contact Us

__    __     ___      _  _   
\ \\ / //   / _ \\   | \| || 
 \ \/ //   | / \ ||  |  ' || 
  \  //    | \_/ ||  | .  || 
   \//      \___//   |_|\_|| 
    `       `---`    `-` -`