Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(499)

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-iframe-in-main-frame-expected.txt

Issue 1931063004: Stop blocking 'http://127.0.0.1/' as mixed content. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Ugh. Created 4 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 unified diff | Download patch
OLDNEW
1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-redirect-http-to-https-frame.html' was loaded ove r HTTPS, but requested an insecure resource 'http://127.0.0.1:8080/security/reso urces/redir.php?url=https://127.0.0.1:8443/security/mixedContent/resources/borin g.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-redirect-http-to-https-frame.html' was loaded ove r HTTPS, but requested an insecure resource 'http://example.test:8080/security/r esources/redir.php?url=https://127.0.0.1:8443/security/mixedContent/resources/bo ring.html'. This content should also be served over HTTPS.
2 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. 2 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.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698