The Great Divorce: How Modern Streaming Broke Its Marriage with HTTP
summary
HTTP streaming now shows concrete breakage: CMCD v2 forces either cache‑busting query parameters or CORS‑triggering headers, signed rotating URLs prevent browser caching, and content‑steering specs mandate switching CDNs so cached segments go unused, creating a 2x network requests performance tax. Practical workarounds include service workers and Cache API to reintroduce client caching, but long‑term fixes require changing CMCD, content‑steering, and HTTP cache/Vary semantics.
AI-written summary · about
chapters (9)
- 0:00HTTP streaming relationship
- 3:33HTTP caching and CORS
- 5:41CMCD media needs
- 8:27Content steering cache-busting
- 12:39Protected media authorization
- 15:09Security models in streaming
- 16:53Service workers for standards
- 18:40HTTP origin policy
- 20:09Q&A
related talks
20mDecentralizing Video Streaming
16mCDN Challenges of HTTP-based Low Latency Live Streaming Delivery
10mEnhancing CDN Performance and Cutting Egress Costs in Large Video Libraries
23mContent delivery sucks, and what you can do about it
19mDoes a multi-CDN setup (truly) requiring switching?
14mStreaming the Web (it's not what you think)
53mCDNs 101: An Introduction to Content Delivery Networks
33mThe Challenges of Testing Video Playback at Scale