LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt - Issue 222153002: Disallow connecting an insecure WebSocket from a secure page.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

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: Update expectation Created 6 years, 8 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:

OLD	NEW
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/websocket/send-empt y.html' was loaded over HTTPS, but ran insecure content from 'ws://127.0.0.1:888 0/echo': this content should also be loaded over HTTPS.

	2

	3 CONSOLE ERROR: line 14: Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over H TTPS.

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.	4 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.

OLD	NEW