Chromium Code Reviews| Index: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt |
| diff --git a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt |
| index 57db5fa5dd6517920aec247eeeedfee02b61850a..29a30478ef48407fa675f6939a64bc6c620be293 100644 |
| --- a/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt |
| +++ b/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-eventsource-in-main-frame-expected.txt |
| @@ -1,2 +1,3 @@ |
| CONSOLE WARNING: Mixed Content: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-eventsource.html' was loaded over HTTPS, but requested an insecure EventSource endpoint 'http://127.0.0.1:8000/eventsource/resources/simple-event-stream.asis'. This content should also be served over HTTPS. |
| +CONSOLE ERROR: EventSource cannot load http://127.0.0.1:8000/eventsource/resources/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 allowed 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.
|
| This test opens a HTTPS window that loads insecure data via EventSource. We should trigger a mixed content callback because the main frame in the window is HTTPS but now has insecure data. |