Index: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
diff --git a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
index db62132fd24d9d4f954240eef8d2743c5c8b8298..31f63eaa5e968f1919f0f138cefdea606a4cc661 100644 |
--- a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
+++ b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
@@ -1,2 +1,2 @@ |
-CONSOLE WARNING: line 4: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but requested an insecure stylesheet 'http://127.0.0.1:8080/security/mixedContent/resources/style.css'. This content should also be served over HTTPS. |
+CONSOLE WARNING: line 4: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but requested an insecure stylesheet 'http://example.test:8080/security/mixedContent/resources/style.css'. This content should also be served over HTTPS. |
This test opens a window that loads an insecure style sheet. We should trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content. |