Index: LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt b/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt |
index eb7f6158ab3c7d11f0c124afcd62be32c4c20828..016fc0732cf37715bc09729676ba58eef767e7c8 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt |
@@ -1,5 +1,3 @@ |
-CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-redirect-https-to-http-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS. |
- |
This test loads a secure iframe that loads an insecure script (but with a tricky redirect). We should trigger a mixed content callback because an active network attacker can end up controling the script. |