Issues with CORS and time-shifted playback

The CORS error is likely not the issue. I have seen some clients report a CORS error on a 404. The request is returning a 404 error because the start time is invalid. The value of the parameter needs to be the actual start time in epoch, or ISO 8601 format. Please read through the documentation for the start/end time formats:

https://docs.aws.amazon.com/mediapackage/latest/ug/time-shifted.html

Requesting "?start=1" means you're requesting content from back in 1970, which will not work. If you use a valid start time, and you have enabled time-shifted playback on the endpoint, that should take care of this.

Thank you for the quick reply Saurav!

Interesting, we tried to setting Timecode Configuration in MediaLive to zerobased which we assumed would allow for "?start=1" as the first frame in the stream starts at 00:00:00. So going forward we should assume that when we want DVR functionality the URL is going to have to be appended with the time the stream started regardless of the timecode?

Hi jerryfleury,

jerryfleury wrote:
So going forward we should assume that when we want DVR functionality the URL is going to have to be appended with the time the stream started regardless of the timecode?

That is correct, the only way to address a section of content in your catchup window a proper timestamp in either epoch or ISO 8601 is required for the start (and optionally end) time.

Thank you for the help everyone!