Index: LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt b/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt |
index c0b47d50ceeb3e987049fb4cec080653e8b43817..81f02d617680a1eb9c57b9da4ecfc5443abfa2fb 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt |
@@ -1,2 +1,4 @@ |
-CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origin is deprecated. |
+CONSOLE ERROR: [blocked] The page at 'https://127.0.0.1:8443/websocket/send-empty.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. |
+ |
+CONSOLE ERROR: line 14: Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS. |
This test opens a HTTPS window that creates an insecure WebSocket connection. We should trigger a mixed content callback because the main frame in the window is HTTPS but is trying connecting to an insecure WebSocket server. |