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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-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 ERROR: line 9: [blocked] The page at 'https://127.0.0.1:8443/security/mi xedContent/resources/frame-with-insecure-iframe.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resource s/boring.html': this content should also be loaded over HTTPS. 1 CONSOLE ERROR: line 9: Mixed Content: The page at 'https://127.0.0.1:8443/securi ty/mixedContent/resources/frame-with-insecure-iframe.html' was loaded over HTTPS , but requested an insecure resource 'http://127.0.0.1:8080/security/mixedConten t/resources/boring.html'. This request has been blocked; the content must be ser ved over HTTPS.
2
3 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this. 2 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698