Index: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-expected.txt |
index a8919c1eddf9789a18d12d750d31c4fe4ab994f2..f21296cc6a8f87d0e313dcf44913c647c0aa9ef7 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-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 loads a secure iframe that loads an insecure iframe. We should get a mixed content callback becase the child frame is HTTPS. |