Chromium Code Reviews

Unified Diff: LayoutTests/http/tests/security/mixedContent/laxChecking/websocket/insecure-websocket-in-secure-page-expected.txt

Issue 566533003: Mixed Content: Make MixedContentChecker completely static. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Fixing tests. Created 6 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Index: LayoutTests/http/tests/security/mixedContent/laxChecking/websocket/insecure-websocket-in-secure-page-expected.txt
diff --git a/LayoutTests/http/tests/security/mixedContent/laxChecking/websocket/insecure-websocket-in-secure-page-expected.txt b/LayoutTests/http/tests/security/mixedContent/laxChecking/websocket/insecure-websocket-in-secure-page-expected.txt
deleted file mode 100644
index a1f80e1cf0d3adb03d788063774bed6998881440..0000000000000000000000000000000000000000
--- a/LayoutTests/http/tests/security/mixedContent/laxChecking/websocket/insecure-websocket-in-secure-page-expected.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/websocket/resources/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.
-
-CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origin is deprecated.
-This is a testharness.js-based test.
-FAIL 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. assert_equals: evt.data expected "DONE" but got "FAIL: No exception was thrown"
-Harness: the test ran to completion.
-

Powered by Google App Engine