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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-texttrack-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: Created 4 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-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. 1 CONSOLE ERROR: Text track from origin 'http://localhost:8000' has been blocked f rom loading by Cross-Origin Resource Sharing policy: The 'Access-Control-Allow-O rigin' header has a value 'http://127.0.0.1:8000' that is not equal to the suppl ied origin. Origin 'https://127.0.0.1:8443' is therefore not allowed access.
2 ALERT: Failed to load. 2 ALERT: Failed to load.
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. 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.
estark 2016/05/02 04:48:46 Same here, looks like either description needs to
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698