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

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

Issue 2900423003: Use origins instead of URLs in console messages about mixed content.
Patch Set: Created 3 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: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-iframe.html' was loaded over HTTPS, but requested an insecure resource 'http://example.test:8080/security/mixedContent/r esources/boring.html'. This content should also be served over HTTPS. 1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/' was loaded over HTTPS, but requested an insecure resource 'http://example.test:8080/securi ty/mixedContent/resources/boring.html'. This content should also be served over HTTPS.
2 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback even though we've set the preference to block this, because w e've overriden the preference via a web permission client callback. 2 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback even though we've set the preference to block this, because w e've overriden the preference via a web permission client callback.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698