Your first request starts here.
Prepare an origin, configure delivery and inspect responses.
This is a connection preparation guide. Set the actual delivery domain, origin and TLS settings before launch. The .example names below are placeholders.
Prepare the origin
Use clear resource paths. The origin should return correct Content-Type and Cache-Control headers. Every URI in an HLS playlist must resolve to a resource accessible through the CDN.
/assets/app.a81f.js
/live/channel-01/master.m3u8
/live/channel-01/720p/index.m3u8
/vod/film-01/master.m3u8Configure delivery
Origin and Host
Set the origin address, HTTP Host and TLS SNI. Verify the origin does not resolve back to the CDN.
Domain and HTTPS
Prepare a certificate for the delivery hostname and point DNS at the agreed target.
Cache policies
Define separate policies for /assets/, /live/ and /vod/. Private responses and access keys require their own policy.
Inspect a response
curl -sS -D - -o /dev/null \
https://media.example/assets/app.a81f.js
curl -sS \
https://media.example/live/channel-01/master.m3u8Repeat the GET request and inspect Cache-Control, Age (if present), Content-Type and CORS. A missing Age header alone does not prove a cache MISS. Then test live playlist updates and VOD seeking in your target player.
Browser playback and CORS
If the site and CDN have different origins, configure CORS for playlists, segments, initialization files and fonts. Public resources without credentials may use Access-Control-Allow-Origin: *. Cookies or authorization require an explicit access policy.