LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-iframe-in-main-frame-expected.txt - Issue 19551006: Re-instantiate the mixed iframe block for M30.

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/redirect-http-to-https-iframe-in-main-frame-expected.txt

Issue 19551006: Re-instantiate the mixed iframe block for M30. (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 7 years, 5 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 MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-redirect-http-to-https-frame.html displayed insecure cont ent from http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0. 1:8443/security/mixedContent/resources/boring.html.	1 CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-redirect-http-to-https-frame.html ran insecure content fr om http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0.1:8443 /security/mixedContent/resources/boring.html.

2	2

3 This test opens a window that loads an insecure iframe (via a tricky redirect). We should trigger a mixed content callback because the main frame in the window is HTTPS but is running content that can be controlled by an active network atta cker.	3 This test opens a window that loads an insecure iframe (via a tricky redirect). We should trigger a mixed content callback because the main frame in the window is HTTPS but is running content that can be controlled by an active network atta cker.

OLD	NEW