Index: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
index 91c40bc746f4369b3cfbe65a2819938e82f5f5d9..00ba869070c789e19164afc4f9c0fa9e9f29b984 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
@@ -1,5 +1,4 @@ |
-CONSOLE WARNING: line 8: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/boring.html': this content should also be loaded over HTTPS. |
- |
+CONSOLE WARNING: line 8: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but requested an insecure resource 'http://127.0.0.1:8080/security/mixedContent/resources/boring.html'. This content should also be served over HTTPS. |
This test opens a window that loads an insecure iframe. We should trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content. |
============== Back Forward List ============== |