This example uses clearKey, but the important bit from your point of view is the existence of the 'ContentProtection' attribute in the manifest. Most DASH protected files will have the information in the manifest and it should be easy to check - it will look like this:
#Safari encrypted connection mp4
![safari encrypted connection safari encrypted connection](https://tipsmake.com/data/images/how-to-fix-errors-cant-establish-secure-connection-on-safari-picture-3-ccNlU90F0.png)
The browser will create an 'encrypted' event and send it back to your application (or to whatever has registered to listen to video events). You can see that the browser detects that the media is encrypted when it receives it from the CDN (not CDM.). Its is specified by W3.org and the following diagram form the latest spec gives a good feel for the flow: BitMovin or JWPlayer, then playback of encrypted content across browsers should 'just work'.ĮME is an extension mechanism that allows the browser build on the HTML5 video capability to detect encrypted content, request the key and using the key decrypt and playback securely the encrypted content.ĮME itself is an API that defines the interacting between the application, browser, media player and CDM (Content Decryption Model). If you are using one of the common 3rd party Javascript players, e.g. Firstly, it is worth saying that all the latest versions of the main browsers support Encrypted Media Extensions (EME) for playing back encrypted streamed video now.