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

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

Powered by Google App Engine
This is Rietveld 408576698