W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2015

Re: [mixed-content] DASH Players and Mixed Content

From: Daniel Weinberger <daniel.weinberger@bitmovin.net>
Date: Thu, 23 Jul 2015 17:46:42 +0200
Message-ID: <CAKwBfzH4PJr6p=wv3fuM2V2FkE5cAHNER_rx7rwJXMEM5wmFkA@mail.gmail.com>
To: public-webappsec <public-webappsec@w3.org>
I work for bitmovin and we develop our own MSE-based MPEG-DASH player
bitdash.

We are facing this problem with many of our customers, so a solution is
very desirable.

Although the idea sounds good, I'm not sure all issues are addressed. For
example to enable DASH we need to download a manifest file, which we need
to parse in JS.
There are also other parts which are probably needed, like
subtitles/captions. They can be files, but they can be also embedded into
ISO BMFF (i.e. mp4) fragments. As the MSE does not support all formats
needed (e.g. WebVTT, TTML, ... / with styling etc.) across browsers, we
need to parse these mp4 fragments in JS. This won't be possible with the
proposed solution as the requested content is not accessible in JS.

I know customers can just put these relatively small files on HTTPS while
serving the actual data using HTTP, most customers want to have all its
content in one place.

However, I cant think of a solution for this, except separating the files.
But maybe the smart guys here find a solution.
Finally I'm not saying these are show stoppers, I just wanted to give some
insights in what is important for us and our customers.

Daniel Weinberger
Received on Thursday, 23 July 2015 15:49:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:13 UTC