Virtual Channel with a CDN

How to configure your CDN for your Virtual Channel service

As a virtual channel can be a combination of content slots and ad breaks slots, the CDN configuration for Virtual Channel can be based on both policies:


πŸ“˜

Summary Table

The typical rules are as follows, in the recommended order:

Rule for

URL pattern

Target origin

Origin policy

Cache policy

Manifests

*

.mpd,

*

.m3u8

stream.broadpeak.io

Forward query params & headers

Expose

Location

header

No caching

SSAT

*

/bpk-sst/

*

stream.broadpeak.io

Forward query params & headers

No caching

Ad Segments

(if managed bybroadpeak.io). Also applies to gap fillers prepared bybroadpeak.io

/bpkio-jitt/

*

stream.broadpeak.io

Forward query params & headers

Cached

Ad Segments

(if pre-packaged)

defined by your ad origin

your ad origin

defined by your ad origin

Cached

Gap filler segments

(if not managed bybroadpeak.io)

defined by your gap filler origin

your gap filler origin

defined by your gap filler origin

Cached

Empty subtitles

/empty.webvtt

stream.broadpeak.io

Forward query params

Cached

Replacement media segments

defined by the replacement origin

the replacement origin

defined by the replacement origin

Cached

Media segments

-

your content origin

defined by your content origin

Cached


What’s Next

Here are some playbooks on how to configure the CDN for your application with specific 3rd party products