| 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 7068f10cc747a611fbb98dcf3128a21c40a784fa..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,5 +1,3 @@
|
| -CONSOLE WARNING: line 1: 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.
|
|
|