I working on a fullscreen slider with video integration (mp4-videos).
Everything is working fine, besides in Safari.
I know that Safari has some problems with the HTML5 video tag, but I tried every solution I could find (muted, playsinline, preload, js(play, pause, …) and nothing works.
After checking the URL of the video in the Dom, I realized that the processed Video doesn’t even work when opening in a new tab.
The url as reference: http://localhost:8081/_Resources/Persistent/8/6/5/9/8659114eb7c515b396830f9c946d8f6a0d164484/test.mov
Has anyone encountered the same problem with processed videos in Safari?
Sorry if my question is a little bit basic, but: If you access the video url alone (as you posted above), does the web server deliver the resource with correct content-type http header?
Can you post the full http response headers – i.e. the result of curl --location --head http://localhost:8081/_Resources/Persistent/8/6/5/9/8659114eb7c515b396830f9c946d8f6a0d164484/test.mov ?
I remember some issues I had with images delivered with wrong content-type headers. “The other browsers” happily ignored the wrong content-type header and instead inferred the actual content type somehow – but not safari. Safari was actually more correct by following my (bad) server advice. So, in my case, safari took the blame too, while it was actually the only browser that correctly adhered to the wrong http response header information.