Restricting Encrypted Media Extensions to secure origins


There is a discussion over on the public-html-media list around a proposal
to restrict EME to secure origins. Input from content publishers especially
is requested.

At least for our service, because browsers do not allow mixed HTTP and
HTTPS content, our site must be served over HTTP because the content is
served over HTTP. Migrating our CDN to HTTPS is a significant undertaking
which we cannot do overnight and I wonder if other content providers are in
a similar position ?

Best regards,

Mark Watson

---------- Forwarded message ----------
From: Joe Steele <>
Date: Wed, Sep 17, 2014 at 12:11 PM
Subject: Feedback requested for bug 26332
To: "<>" <>

This bug is stuck without a clear decision. It would be very helpful if we
could get more feedback from the larger Media task force, especially
content publishers who would be most impacted by this in my opinion.

Joe Steele

Received on Wednesday, 17 September 2014 21:17:30 UTC