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

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

Issue 222153002: Disallow connecting an insecure WebSocket from a secure page. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Rebase Created 6 years, 7 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
1 CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origi n is deprecated. 1 CONSOLE ERROR: [blocked] The page at 'https://127.0.0.1:8443/security/mixedConte nt/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 a lso be loaded over HTTPS.
2 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. 2
3 This is a testharness.js-based test.
4 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 th e window is HTTPS but is trying connecting to an insecure WebSocket server.
5 Harness: the test ran to completion.
6
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698