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 forURL patternTarget originOrigin policyCache policy
Manifests*.mpd, *.m3u8stream.broadpeak.ioForward query params & headers

Expose Location header
No caching
SSAT*/bpk-sst/*stream.broadpeak.ioForward query params & headers No caching
Ad Segments
(if managed by broadpeak.io). Also applies to gap fillers prepared by broadpeak.io
/bpkio-jitt/*stream.broadpeak.ioForward query params & headersCached
Ad Segments
(if pre-packaged)
defined by your ad originyour ad origindefined by your ad originCached
Gap filler segments
(if not managed by broadpeak.io)
defined by your gap filler originyour gap filler origindefined by your gap filler originCached
Empty subtitles/empty.webvttstream.broadpeak.ioForward query paramsCached
Replacement media segmentsdefined by the replacement originthe replacement origindefined by the replacement originCached
Media segments-your content origindefined by your content originCached

What’s Next

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