third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt - Issue 2900423003: Use origins instead of URLs in console messages about mixed content.

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: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt

Issue 2900423003: Use origins instead of URLs in console messages about mixed content.

Patch Set: Created 3 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:

OLD	NEW
1 CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixed Content/resources/frame-with-insecure-iframe.html' was loaded over HTTPS, but re quested an insecure resource 'http://example.test:8080/security/mixedContent/res ources/boring.html'. This request has been blocked; the content must be served o ver HTTPS.	1 CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/' was loaded o ver HTTPS, but requested an insecure resource 'http://example.test:8080/security /mixedContent/resources/boring.html'. This request has been blocked; the content must be served over HTTPS.

2 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this.	2 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this.

OLD	NEW