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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-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 ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixed Content/resources/frame-with-insecure-iframe.html' was loaded over HTTPS, but re quested an insecure resource 'http://127.0.0.1:8080/security/mixedContent/resour ces/boring.html'. This request has been blocked; the content must be served over HTTPS. 1 CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixed Content/resources/frame-with-insecure-iframe.html' was loaded over HTTPS, but re quested an insecure resource 'http://example.test:8080/security/mixedContent/res ources/boring.html'. This request has been blocked; the content must be served o ver HTTPS.
2 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this. 2 This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698