| 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 bf07286921a3c8a8fcf35fd854fe23e9b5944af1..b384e049fda88363d2256d6bdc05ad9315120c76 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,3 +1,3 @@
|
| -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 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.
|
|
|