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 bb55e6aa9c9fc1981e9fcee288c65536de11185e..ec36f0bf47950cff52cba96788459ce541ec1ad2 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,3 +1,5 @@ |
+CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-frame.html ran insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html. |
+ |
This test loads a secure iframe that loads an insecure iframe. We should *not* get a mixed content callback becase the main frame is HTTP and the grandchild iframe doesn't contaminate the child iframe's security origin with mixed content. |