<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking"
href="https://bugs.webkit.org/show_bug.cgi?id=145717#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking"
href="https://bugs.webkit.org/show_bug.cgi?id=145717">bug 145717</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>Note that the WIP mixed content spec strongly implies that we should fire the XHR's onerror event when we block it, but it doesn't actually tell us to do so: it seems to presume that we're *already* doing it [1]. I couldn't find a specification for that anywhere, but is seems like the Right Thing.
I have a patch for this in <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - XHR should be treated as active mixed content"
href="show_bug.cgi?id=140793">bug #140793</a>, but the patch is old and not completely right: it causes two mixed content warnings to be emitted for just one XHR. I think the spurious one is coming from the CachedResourceLoader. Unfortunately I don't plan to work on this more in the near future.
[1] <a href="http://www.w3.org/TR/mixed-content/#websockets-integration">http://www.w3.org/TR/mixed-content/#websockets-integration</a></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>