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

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

Issue 561153002: Mixed Content: Migrate ResourceFetcher to the static mixed content checker. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Fixing comment and test. Created 6 years, 3 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 | Annotate | Revision Log
OLDNEW
1 CONSOLE WARNING: line 8: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-redirect-http-to-https-frame.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/boring.html': thi s content should also be loaded over HTTPS. 1 CONSOLE WARNING: line 8: Mixed Content: The page at 'https://127.0.0.1:8443/secu rity/mixedContent/resources/frame-with-redirect-http-to-https-frame.html' was lo aded over HTTPS, but requested an insecure resource 'http://127.0.0.1:8080/secur ity/resources/redir.php?url=https://127.0.0.1:8443/security/mixedContent/resourc es/boring.html'. This content should also be served over HTTPS.
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. 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