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

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

Issue 561153002: Mixed Content: Migrate ResourceFetcher to the static mixed content checker. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Fixing comment and test. Created 6 years, 3 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 ERROR: [blocked] The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-texttrack.html' was loaded over HTTPS, but ran insecure content from 'http://localhost:8000/security/resources/captions-with-ac cess-control-headers.php?origin=1': this content should also be loaded over HTTP S. 1 CONSOLE ERROR: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixed Content/resources/frame-with-insecure-texttrack.html' was loaded over HTTPS, but requested an insecure Text Track 'http://localhost:8000/security/resources/capt ions-with-access-control-headers.php?origin=1'. This request has been blocked; t he content must be served over HTTPS.
2
3 ALERT: Failed to load. 2 ALERT: Failed to load.
4 This test opens a window that loads an insecure track. We should trigger a mixed content callback as the main frame in the window is HTTPS and is running insecu re track. 3 This test opens a window that loads an insecure track. We should trigger a mixed content callback as the main frame in the window is HTTPS and is running insecu re track.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698