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

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

Issue 2900423003: Use origins instead of URLs in console messages about mixed content.
Patch Set: Created 3 years, 7 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 ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixed Content/resources/frame-with-data-url-frame-with-script.html' was loaded over HT TPS, but requested an insecure script 'http://example.test:8080/security/mixedCo ntent/resources/script.js'. This request has been blocked; the content must be s erved over HTTPS. 1 CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/' was loaded o ver HTTPS, but requested an insecure script 'http://example.test:8080/security/m ixedContent/resources/script.js'. This request has been blocked; the content mus t be served over HTTPS.
2 This test opens a window that loads a data: iframe that loads an insecure script , and that the script is still blocked. Although the data: frame has a separate origin, the script can still navigate top. 2 This test opens a window that loads a data: iframe that loads an insecure script , and that the script is still blocked. Although the data: frame has a separate origin, the script can still navigate top.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698