LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt - Issue 351163002: Prevent sandboxed iframes from bypassing WebSocket mixed content checks.

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

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

Issue 351163002: Prevent sandboxed iframes from bypassing WebSocket mixed content checks. (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Test. Created 6 years, 6 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 side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page.html ('k') | LayoutTests/http/tests/security/mixedContent/websocket/resources/expect-throw-on-construction.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt

diff --git a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt b/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt

similarity index 64%

copy from LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt

copy to LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt

index 6b777ea9e2bf6d43e5eee699ebd29b5ee474f3a6..939bcd2729d5cf8fd5f295c2b45498f50145fb4c 100644

--- a/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt

+++ b/LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-sandbox-in-secure-page-expected.txt

@@ -1,4 +1,4 @@

-CONSOLE ERROR: [blocked] 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 ERROR: [blocked] The page at 'https://127.0.0.1:8443/security/mixedContent/websocket/resources/sandboxed-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.

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.