Chromium Code Reviews

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

Issue 302063002: Always preload all tokens before parsing (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Fix CORS issue with preloader Created 6 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View unified diff | | Annotate | Revision Log
OLDNEW
1 CONSOLE WARNING: line 1: 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
1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-script.html' was loaded over HTTPS, but ran insecure co ntent from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': th is content should also be loaded over HTTPS. 3 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-script.html' was loaded over HTTPS, but ran insecure co ntent from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': th is content should also be loaded over HTTPS.
2 4
3 This test loads a secure iframe that loads an insecure script. We should trigger a mixed content callback even though the main frame is HTTP because the HTTPS f rame's origin is contaminated with an insecure script. 5 This test loads a secure iframe that loads an insecure script. We should trigger a mixed content callback even though the main frame is HTTP because the HTTPS f rame's origin is contaminated with an insecure script.
4 6
5 7
OLDNEW

Powered by Google App Engine