Cache tuning for large video objects
Large video files break naive caching. A single 4 GB asset can evict thousands of small objects if your policy treats everything the same, and a cold player seeking to the middle of a file should not force a full origin pull.
Two defaults do most of the work. First, honour range requests end to end so players fetch only the bytes they need. Second, use stale-while-revalidate generously: serve the cached object immediately and refresh it in the background, so a slow origin never becomes a slow viewer.
On our edge both are on by default. If you are migrating a VOD catalogue, keep your existing Cache-Control and watch the hit ratio climb over the first few hours as the working set warms.