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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt

Issue 1931063004: Stop blocking 'http://127.0.0.1/' as mixed content. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Ugh. Created 4 years, 6 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
OLDNEW
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. 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://example.test:8080/security/mixedCo ntent/resources/style.css'. This content should also be served over HTTPS.
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. 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.
3 3
4 4
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698