Netflix, MSE, and EME

Here are some presumed facts:

* Service workers require TLS.
* Since we do not want service workers to affect legacy mixed content,
fetch() with mode /no CORS/ can still fetch non-TLS content. The
response to this is an opaque blob. (I don't like this, but Jake tells
me this is how Chrome will do it.)
* Netflix does not care about reading the contents of a response, it
just wants to feed it into <video>.

Given this, if we enable MSE to work with opaque responses, EME can
require TLS, and Netflix can use TLS, while still not using it for


Received on Friday, 14 November 2014 22:49:56 UTC