Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(477)

Side by Side 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. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/webso cket/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 l oaded over HTTPS.
2
3 CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origi n is deprecated.
4 This is a testharness.js-based test.
5 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 th e window is HTTPS but is trying connecting to an insecure WebSocket server. asse rt_equals: evt.data expected "DONE" but got "FAIL: No exception was thrown"
6 Harness: the test ran to completion.
7
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698