Index: LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt b/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt |
deleted file mode 100644 |
index 939bcd2729d5cf8fd5f295c2b45498f50145fb4c..0000000000000000000000000000000000000000 |
--- a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt |
+++ /dev/null |
@@ -1,6 +0,0 @@ |
-CONSOLE ERROR: [blocked] The page at 'https://127.0.0.1:8443/security/mixedContent/websocket/resources/sandboxed-expect-throw-on-construction.html' was loaded over HTTPS, but ran insecure content from 'ws://127.0.0.1:8880/echo': this content should also be loaded over HTTPS. |
- |
-This is a testharness.js-based test. |
-PASS Test that when a HTTPS window that creates an insecure WebSocket connection is opened, the mixed content callback is triggered because the main frame in the window is HTTPS but is trying connecting to an insecure WebSocket server. |
-Harness: the test ran to completion. |
- |