W3C home > Mailing lists > Public > public-html-media@w3.org > October 2014

Re: [EME] Mitigating the impact of HTTPS on content providers

From: Henri Sivonen <hsivonen@hsivonen.fi>
Date: Mon, 27 Oct 2014 16:29:45 +0200
Message-ID: <CANXqsRJUn-0pUZnGt=a3aMk3D=MnqHS_VFKkwi21nKUG_C7PXw@mail.gmail.com>
To: David Dorwin <ddorwin@google.com>
Cc: "public-html-media@w3.org" <public-html-media@w3.org>
On Fri, Oct 24, 2014 at 7:53 PM, David Dorwin <ddorwin@google.com> wrote:
> Temporarily allow Mixed Content XHRs to be provided to MSE when EME is in
> use.

How do you track the "provided to MSE" part? Having the browser keep
track that data from mixed-content XHR travels only to MSE doesn't
seem particularly attractive.

Better alternative: Before the XHR request is sent, allow the
application to set a content type expectation and a response body hash
expectation on XHR. If these are set, mixed-content XHR is attempted.
If the response content type matches the content type expectation and
a hash computed over the response body matches the hash expectation,
the attempted XHR does not fail and the application is allowed to use
the retrieved data in any way possible with XHR normally after the
load has been completed (it has to complete for the hash to be
checked), including passing the data to MSE.

-- 
Henri Sivonen
hsivonen@hsivonen.fi
https://hsivonen.fi/
Received on Monday, 27 October 2014 14:30:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:55 UTC