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

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

Issue 26770004: Add console message levels to test expectation output. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Tests. Created 7 years, 2 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 | Annotate | Revision Log
OLDNEW
1 CONSOLE MESSAGE: [blocked] The page at 'https://127.0.0.1:8443/security/mixedCon tent/resources/frame-with-insecure-script.html' was loaded over HTTPS, but ran i nsecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/scri pt.js': this content should also be loaded over HTTPS. 1 CONSOLE ERROR: [blocked] The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-script.html' was loaded over HTTPS, but ran ins ecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/script .js': this content should also be loaded over HTTPS.
2 2
3 This test opens a window that loads an insecure script. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is running insecure scripts, because we've set the preference to block this. 3 This test opens a window that loads an insecure script. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is running insecure scripts, because we've set the preference to block this.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698