LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-main-frame-expected.txt - WebKit - Git at Google

 CONSOLE MESSAGE: line 24: [blocked] The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-websocket.html was not allowed to run insecure content from ws://127.0.0.1:8880/websocket/tests/hybi/echo.

 ALERT: WebSocket connection failed.
 CONSOLE MESSAGE: line 14: WebSocket connection failed: WebSocket is closed before the connection is established.
 This test opens a window that connects to an insecure ws:// WebSocket. We should block the connection and trigger a mixed content callback because the main frame is HTTPS, but the data sent over the socket could be recorded or controlled by an attacker.
	CONSOLE MESSAGE: line 24: [blocked] The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-websocket.html was not allowed to run insecure content from ws://127.0.0.1:8880/websocket/tests/hybi/echo.

	ALERT: WebSocket connection failed.
	CONSOLE MESSAGE: line 14: WebSocket connection failed: WebSocket is closed before the connection is established.
	This test opens a window that connects to an insecure ws:// WebSocket. We should block the connection and trigger a mixed content callback because the main frame is HTTPS, but the data sent over the socket could be recorded or controlled by an attacker.