<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [EFL][GTK] http/tests/media/clearkey/clear-key-hls-aes128.html is timeout since r79641"
href="https://bugs.webkit.org/show_bug.cgi?id=141959#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [EFL][GTK] http/tests/media/clearkey/clear-key-hls-aes128.html is timeout since r79641"
href="https://bugs.webkit.org/show_bug.cgi?id=141959">bug 141959</a>
from <span class="vcard"><a class="email" href="mailto:jer.noble@apple.com" title="Jer Noble <jer.noble@apple.com>"> <span class="fn">Jer Noble</span></a>
</span></b>
<pre>Philipe,
The unrecognized scheme "clearkey:" is a trigger to begin the EME code path. If you change it to just crypt0.key, and your HLS back-end fetches, decrypts, and displays the media stream, there will be no 'needkey' message to signal the client to fetch and add key data through the EME APIs.
In OS X, the AVFoundation APIs give us a notification that there is media data that cannot be retrieved through HTTP(s), providing us the "clearkey:crypt0.key" URI. Perhaps there is something similar in the hlsdemux libraries?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>