Index: LayoutTests/http/tests/security/mixedContent/insecure-script-in-iframe-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-script-in-iframe-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-script-in-iframe-expected.txt |
index 486d9683038ed97ef23d946b44a8e11049529bd5..61555b22560a0e4a0e40d4fb58298dd912f39a0a 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-script-in-iframe-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-script-in-iframe-expected.txt |
@@ -1,5 +1,4 @@ |
-CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-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. |
- |
+CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-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. We should trigger a mixed content callback even though the main frame is HTTP because the HTTPS frame's origin is contaminated with an insecure script. |