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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-frame-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-frame.html' was loaded over HTT PS, but requested an insecure resource 'http://example.test:8080/security/mixedC ontent/resources/boring.html'. This request has been blocked; the content must b e served 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 resource 'http://example.test:8080/security /mixedContent/resources/boring.html'. This request has been blocked; the content must be served over HTTPS.
2 This test opens a window that loads a data: iframe that loads an insecure frame, and that the frame is still blocked. 2 This test opens a window that loads a data: iframe that loads an insecure frame, and that the frame is still blocked.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698