| Index: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..f7d29954b386821ef15f6204faee209ef790777b
|
| --- /dev/null
|
| +++ b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt
|
| @@ -0,0 +1,5 @@
|
| +CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/websocket/resources/sandboxed-expect-throw-on-construction.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://127.0.0.1:8880/echo'. This request has been blocked; this endpoint must be available over WSS.
|
| +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.
|
| +
|
|
|