Apply strict blocking of active mixed content in HTTPS subframes only

third_party/WebKit/LayoutTests/http/tests/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https-expected.txt

Index: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https-expected.txt b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7ccfaa114e0963e579ee3542668110622e2719d2
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https-expected.txt
@@ -0,0 +1,9 @@
+CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https.html' was loaded over HTTPS, but requested an insecure resource 'http://127.0.0.1:8000/security/mixedContent/resources/frame-loads-insecure-script.html'. This content should also be served over HTTPS.

[estark, 2016/02/26 01:17:59]

Is this (the -expected.txt file) the right way to account for console output in
a testharness test?

[Mike West, 2016/02/26 08:43:02]

Yes, that works just fine.

+CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/active-subresource-in-http-iframe-not-blocked.https.html' was loaded over HTTPS, but requested an insecure script 'http://127.0.0.1:8000/security/mixedContent/resources/script-post-message.js'. This content should also be served over HTTPS.
+This test passes if the active subresource in the frame below is allowed.
+
+
+This is a testharness.js-based test.
+PASS Testing an insecure script in a mixed iframe 
+Harness: the test ran to completion.
+