Cloudfront serves stale manifest for the DVR playback

Question

We are having an issue in our platform where stale manifest is served for the DVR/Start-over playback requests.
This creates inconsistency in the DVR DASH playback when the manifest changes from type=Dynamic to type=Static.

From our observation, at times, when the end time of startover and the playback request don’t align perfectly, the last manifest from origin is of type=dynamic, but max=age=21600. This result in Cloudfront caching this manifest, and returning to the subsequent requests.
We need a means to not cache the manifest during this transition.
We are looking at using cache-control: stale-while-validate or max=age , or some other options to correct the behaviour.

Answer

Hi - May be you can explore stale-while-revalidate and stale-if-error cache control directives. stale-while-revalidate is ideal for content that refreshes frequently or unpredictably, or where content requires significant time to regenerate, and where having the latest version of the content is not essential. The stale-if-error directive enhances the user experience and improves availability by serving stale content when origins return an error.

Cloudfront serves stale manifest for the DVR playback

相關內容