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 f1a390982da51c459a12845aa2d21b24f5d60da3..7fc1fad79e9bebcf394b195193fc0f4a24f33cf1 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,4 +1,4 @@ |
-CONSOLE MESSAGE: 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: 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. |
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. |