Hi, it's me and yet another obscure problem :)
We have an option to add a video to a composed email on our website, and it's added to the email body as a direct link to the video file on server (https://embed-cdn.ziggeo.com/v1/applications/<app token>/videos/<video token>/video.mp4).
The users click the link and expect it to open and play in their browser, and that's what usually happens, but not always. From time to time it switches to always downloading the video file instead of playing for no apparent reason (same browser, same browser settings, same video file), and then switches back to playing. And it happens often enough that the users notice and think that something went wrong :)
It just happened to me, too, so I've compared the headers. The requests are identical, except for the actual IP address of the remote server, and the content-type of the response - it flips between video/mp4 and application/webm, which, in turn, means the difference between playing in browser or downloading as file, and that, in turn, means that the user experience kind of depends on which server has been picked by AWS load balancer :). Edited: actually, it looks like any server can return either video/mp4 or application/webm as content type for any given file (serves me right for looking for patterns in all the wrong places :))
Now, I understand that you probably have little control of what Cloudfront does when anyone accesses files stored there, but I'm still posting this in case you've encountered anything like this before and maybe know why it seems to give different content types for the same file in the first place :)
I can send full request/response headers to the support email, if that helps.
Thank you in advance!
Please sign in to leave a comment.