| Index: LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked-expected.txt
|
| diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked-expected.txt
|
| index bbc1131146d7aac19e153b088f2fc98adae00892..70b5806a4419778e81e684e18395d2530277e2ad 100644
|
| --- a/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked-expected.txt
|
| +++ b/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-blocked-expected.txt
|
| @@ -1,2 +1,2 @@
|
| -CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-image.html' was loaded over HTTPS, but requested an insecure image 'http://127.0.0.1:8080/security/resources/compass.jpg'. This request has been blocked; the content must be served over HTTPS.
|
| +CONSOLE ERROR: line 9: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-image.html' was loaded over HTTPS, but requested an insecure image 'http://127.0.0.1:8080/security/resources/compass.jpg'. This request has been blocked; the content must be served over HTTPS.
|
| This test opens a window that loads an insecure image. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this.
|
|
|