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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-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 4: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecu re content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css ': this content should also be loaded over HTTPS. 1 CONSOLE WARNING: line 4: Mixed Content: The page at 'https://127.0.0.1:8443/secu rity/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but requested an insecure stylesheet 'http://127.0.0.1:8080/security/mixedConte nt/resources/style.css'. This content should also be served over HTTPS.
2
3 This test loads a secure iframe that loads an insecure style sheet. We should tr igger a mixed content callback because an active network attacker can use CSS3 t o breach the confidentiality of the HTTPS security origin. 2 This test loads a secure iframe that loads an insecure style sheet. We should tr igger a mixed content callback because an active network attacker can use CSS3 t o breach the confidentiality of the HTTPS security origin.
4 3
5 4
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698