third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt - Issue 2198933003: Prevent mixed content iframes on back/forward.

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-expected.txt

Issue 2198933003: Prevent mixed content iframes on back/forward. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 4 years, 4 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

OLD	NEW
1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but r equested an insecure resource 'http://example.test:8080/security/mixedContent/re sources/boring.html'. This content should also be served over HTTPS.	1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but r equested an insecure resource 'http://example.test:8080/security/mixedContent/re sources/boring.html'. This content should also be served over HTTPS.

2 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback because the main frame in the window is HTTPS but is running insecure content.	2 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback because the main frame in the window is HTTPS but is running insecure content.

3	3

4 ============== Back Forward List ==============	4 ============== Back Forward List ==============

5 curr-> http://127.0.0.1:8000/security/mixedContent/insecure-iframe-in-main-fram e.html	5 curr-> http://127.0.0.1:8000/security/mixedContent/insecure-iframe-in-main-fram e.html

6 ===============================================	6 ===============================================

7	7

8 ============== Back Forward List ==============	8 ============== Back Forward List ==============

9 curr-> https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecu re-frame.html	9 curr-> https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecu re-frame.html

	10 http://example.test:8080/security/mixedContent/resources/boring.html (in frame "<!--framePath //<!--frame0-->-->")
	Charlie Reis 2016/08/01 23:39:16 This frame should show up now that we're not artif This frame should show up now that we're not artificially excluding it from history. That seems like the right thing to do.
10 ===============================================	11 ===============================================

OLD	NEW

« no previous file with comments | « no previous file | third_party/WebKit/Source/core/loader/FrameLoader.cpp » ('j') | third_party/WebKit/Source/core/loader/FrameLoader.cpp » ('J')