LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt - Issue 302063002: Always preload all tokens before parsing

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

Issue 302063002: Always preload all tokens before parsing (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Fix CORS issue with preloader Created 6 years, 7 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

« LayoutTests/fast/dom/HTMLScriptElement/dont-load-unknown-type-expected.txt ('K') | « LayoutTests/http/tests/security/mixedContent/insecure-script-in-main-frame-blocked-expected.txt ('k') | LayoutTests/tables/mozilla_expected_failures/bugs/bug128876-expected.txt » ('j') | Source/core/html/parser/HTMLDocumentParser.cpp » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt

diff --git a/LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt b/LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt

index e1d9f57df50e5fdeedd9bdc71ee8baa2e5398069..b71075dc6e83ce955acd3ce5c670dd8f06705d2d 100644

--- a/LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt

+++ b/LayoutTests/http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe-expected.txt

@@ -1,3 +1,5 @@

+CONSOLE WARNING: line 1: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-redirect-http-to-https-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0.1:8443/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-redirect-http-to-https-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0.1:8443/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS.

This test loads a secure iframe that loads an insecure script (but with a tricky redirect). We should trigger a mixed content callback because an active network attacker could have redirected the script load to https://attacker.com.