[Webkit-unassigned] [Bug 145717] It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=145717

--- Comment #2 from Michael Catanzaro <mcatanzaro at igalia.com> ---
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 bug #140793, 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] http://www.w3.org/TR/mixed-content/#websockets-integration

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150608/4b990591/attachment.html>