Index: LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-allowed-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-allowed-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-allowed-expected.txt |
index 1abd83e2bbb917560a31dfbc9e02acf9f42cc2ce..001dc57f9e202aeb529fa6126a50a3224ddd6cf9 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-allowed-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-allowed-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-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS. |
- |
CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS. |
This test opens a window that loads an insecure script. We should trigger a mixed content callback even though we've set the preference to block this, because we've overriden the preference via a web permission client callback. |