Delivery

Request flow

A player resolves the delivery host, requests the master playlist, then walks the rendition playlist and pulls segments in order. Nothing on this host is browsable: every path is derived from a manifest the player already holds.

Cache behaviour

Segments answer with a long max-age because their paths are content-addressed. Playlists answer with a short max-age so a ladder change reaches players within one segment duration.

Failure handling

A missing segment answers 404 and the player falls back to the next rendition down the ladder. Repeated misses on the same rendition drop it from the playlist until the origin catches up.

Path shapes served by this node

GET /hls/live/playlist/<key>
GET /hls/live/rendition/<key>
GET /api/v4/stream/manifest/<key>
GET /api/v4/stream/segment/<key>