4 ms·

In browsers at least, DRM doesn't work if your full page doesn't use HTTPS. The encrypted media extensions (EME) are only available on secure contexts, which m

In browsers at least, DRM doesn't work if your full page doesn't use HTTPS. The encrypted media extensions (EME) are only available on secure contexts, which means the page needs to be HTTPS. Segments are typically fetched with standard XHR/fetch, which means they need to use HTTPS on secure origins as well. You really don't want to have to deal with mixed content. Unrelated to DRM, Apple's ATS on iOS kinda requires developers to only use HTTPS origins in their apps. At that point, you might as well just do HTTPS everywhere.

MaxBarraclough 6y ago
> encrypted media extensions (EME) are only available on secure contexts, which means the page needs to be HTTPS I didn't know that, but you're right. [0] There was a time Netflix didn't use HTTPS. [1] I guess they must not have supported HTML5 at that time, and must have been using Silverlight for in-browser viewing. [0] https://www.w3.org/TR/encrypted-media/#privacy-secureorigin https://www.w3.org/TR/encrypted-media/#privacy-secureorigin [1] https://arstechnica.com/information-technology/2015/04/it-wasnt-easy-but-netflix-will-soon-use-https-to-secure-video-streams/ https://arstechnica.com/information-technology/2015/04/it-wa...