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

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

Issue 18104009: Mixed content iframe checks should use top (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Drop back to canDisplay Created 7 years, 5 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 main frame - didStartProvisionalLoadForFrame 1 main frame - didStartProvisionalLoadForFrame
2 main frame - didFinishDocumentLoadForFrame 2 main frame - didFinishDocumentLoadForFrame
3 main frame - didHandleOnloadEventsForFrame 3 main frame - didHandleOnloadEventsForFrame
4 main frame - didFinishLoadForFrame 4 main frame - didFinishLoadForFrame
5 main frame - didCommitLoadForFrame 5 main frame - didCommitLoadForFrame
6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame 6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame
7 CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-redirect-http-to-https-frame.html ran insecure content fr om http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0.1:8443 /security/mixedContent/resources/boring.html. 7 CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-redirect-http-to-https-frame.html displayed insecure cont ent from http://127.0.0.1:8080/security/resources/redir.php?url=https://127.0.0. 1:8443/security/mixedContent/resources/boring.html.
8 8
9 didRunInsecureContent 9 didDisplayInsecureContent
10 main frame - didFinishDocumentLoadForFrame 10 main frame - didFinishDocumentLoadForFrame
11 frame "<!--framePath //<!--frame0-->-->" - didReceiveServerRedirectForProvisiona lLoadForFrame 11 frame "<!--framePath //<!--frame0-->-->" - didReceiveServerRedirectForProvisiona lLoadForFrame
12 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame 12 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame
13 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame 13 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame
14 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame 14 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame
15 main frame - didHandleOnloadEventsForFrame 15 main frame - didHandleOnloadEventsForFrame
16 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame 16 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame
17 main frame - didFinishLoadForFrame 17 main frame - didFinishLoadForFrame
18 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. 18 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