XHR should not be permitted to open HTTP URLs when active mixed content is blocked, and should trigger mixed content warnings otherwise.
Created attachment 245175 [details] Patch
Created attachment 245482 [details] Block mixed content XHR
Comment on attachment 245482 [details] Block mixed content XHR Attachment 245482 [details] did not pass mac-wk2-ews (mac-wk2): Output: http://webkit-queues.appspot.com/results/4810588546924544 New failing tests: http/tests/security/mixedContent/ssl/insecure-xhr-in-main-frame.html http/tests/security/mixedContent/ssl/insecure-xhr-in-iframe.html
Created attachment 245488 [details] Archive of layout-test-results from ews105 for mac-mavericks-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews105 Port: mac-mavericks-wk2 Platform: Mac OS X 10.9.5
Comment on attachment 245482 [details] Block mixed content XHR Attachment 245482 [details] did not pass mac-ews (mac): Output: http://webkit-queues.appspot.com/results/5909659940552704 New failing tests: http/tests/security/mixedContent/ssl/insecure-xhr-in-main-frame.html http/tests/security/mixedContent/ssl/insecure-xhr-in-iframe.html
Created attachment 245490 [details] Archive of layout-test-results from ews101 for mac-mavericks The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: ews101 Port: mac-mavericks Platform: Mac OS X 10.9.5
This is fixed by bug #142378. Also, I think my changes were not ideal anyway: see bug #140625.