Upstream version 10.39.225.0

[platform/framework/web/crosswalk.git] / src / third_party / WebKit / LayoutTests / http / tests / security / mixedContent / redirect-https-to-http-script-in-iframe-expected.txt

diff --git a/src/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt b/src/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt
index eb7f615..016fc07 100644 (file)
--- a/src/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt
+++ b/src/third_party/WebKit/LayoutTests/http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe-expected.txt
@@ -1,5 +1,3 @@
-CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-redirect-https-to-http-script.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/script.js': this content should also be loaded over HTTPS.
-
 This test loads a secure iframe that loads an insecure script (but with a tricky redirect). We should trigger a mixed content callback because an active network attacker can end up controling the script.