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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt

Issue 1940593002: Make sure the test finishes after EventSource loading has completed. (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 WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-eventsource.html' was loaded over HTTPS, but requested an insecure EventSource endpoint 'http://127.0.0.1:8000/eventsour ce/resources/simple-event-stream.asis'. This content should also be served over HTTPS. 1 CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mix edContent/resources/frame-with-insecure-eventsource.html' was loaded over HTTPS, but requested an insecure EventSource endpoint 'http://127.0.0.1:8000/eventsour ce/resources/simple-event-stream.asis'. This content should also be served over HTTPS.
2 CONSOLE ERROR: EventSource cannot load http://127.0.0.1:8000/eventsource/resourc es/simple-event-stream.asis. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://127.0.0.1:8443' is therefore not allo wed access.
dcheng 2016/04/29 22:41:22 Hmm, this doesn't really seem like part of the tes
Łukasz Anforowicz 2016/04/29 23:54:49 Done.
2 This test opens a HTTPS window that loads insecure data via EventSource. We shou ld trigger a mixed content callback because the main frame in the window is HTTP S but now has insecure data. 3 This test opens a HTTPS window that loads insecure data via EventSource. We shou ld trigger a mixed content callback because the main frame in the window is HTTP S but now has insecure data.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698