Index: LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt |
index 5d27f56281fc3a13e0e36de25b83a1d26654fcd3..8bc02467a02027e6e269bc975db2ecd6d6dc1c73 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt |
@@ -1,4 +1,4 @@ |
-CONSOLE MESSAGE: line 4: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css': this content should also be loaded over HTTPS. |
+CONSOLE WARNING: line 4: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css': this content should also be loaded over HTTPS. |
This test loads a secure iframe that loads an insecure style sheet. We should trigger a mixed content callback because an active network attacker can use CSS3 to breach the confidentiality of the HTTPS security origin. |