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 016fc0732cf37715bc09729676ba58eef767e7c8..3ebdc43046a2c41d64b629209f6b055ce738b079 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,3 +1,4 @@ |
+CONSOLE WARNING: Mixed Content: 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 requested an insecure script 'http://127.0.0.1:8080/security/mixedContent/resources/script.js'. This content should also be served 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. |