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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page.html

Issue 222153002: Disallow connecting an insecure WebSocket from a secure page. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Update expectation Created 6 years, 8 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
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 <html> 1 <html>
2 <body> 2 <body>
3 <script> 3 <script>
4 if (window.testRunner) { 4 if (window.testRunner) {
5 testRunner.waitUntilDone(); 5 testRunner.waitUntilDone();
6 testRunner.dumpAsText(); 6 testRunner.dumpAsText();
7 testRunner.setCanOpenWindows(); 7 testRunner.setCanOpenWindows();
8 testRunner.setCloseRemainingWindowsWhenComplete(true); 8 testRunner.setCloseRemainingWindowsWhenComplete(true);
9 testRunner.overridePreference("WebKitAllowRunningInsecureContent", true); 9 testRunner.overridePreference("WebKitAllowRunningInsecureContent", false);
yhirano 2014/04/03 04:53:14 Can you add a test that sets WebKitAllowRunningIns
tyoshino (SeeGerritForStatus) 2014/04/11 19:27:21 Done.
10 } 10 }
11 11
12 window.addEventListener("message", function (e) { 12 window.addEventListener("message", function (e) {
13 if (window.testRunner) 13 if (window.testRunner)
14 testRunner.notifyDone(); 14 testRunner.notifyDone();
15 }, false); 15 }, false);
16 16
17 </script> 17 </script>
18 <p>This test opens a HTTPS window that creates an insecure WebSocket connection. We should 18 <p>This test opens a HTTPS window that creates an insecure WebSocket connection. We should
19 trigger a mixed content callback because the main frame in the window is HTTPS b ut 19 trigger a mixed content callback because the main frame in the window is HTTPS b ut
20 is trying connecting to an insecure WebSocket server.</p> 20 is trying connecting to an insecure WebSocket server.</p>
21 <script> 21 <script>
22 window.open("https://127.0.0.1:8443/websocket/send-empty.html"); 22 window.open("https://127.0.0.1:8443/websocket/send-empty.html");
23 </script> 23 </script>
24 </body> 24 </body>
25 </html> 25 </html>
OLDNEW
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/websocket/insecure-websocket-in-secure-page-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698