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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-xhr-in-main-frame.html

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: Ugh. Created 4 years, 6 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
(Empty)
1 <html>
2 <body>
3 <script>
4 if (window.testRunner) {
5 testRunner.waitUntilDone();
6 testRunner.dumpAsText();
7 testRunner.setCanOpenWindows();
8 testRunner.setCloseRemainingWindowsWhenComplete(true);
9 testRunner.overridePreference("WebKitAllowRunningInsecureContent", true);
10 }
11
12 window.addEventListener("message", function (e) {
13 if (window.testRunner)
14 testRunner.notifyDone();
15 }, false);
16
17 </script>
18 <p>This test opens a HTTPS window that loads insecure data via XHR. We should
19 trigger a mixed content callback because the main frame in the window is HTTPS b ut
20 now has insecure data.</p>
21 <script>
22 window.open("https://127.0.0.1:8443/xmlhttprequest/access-control-response-with- body.html");
23 </script>
24 </body>
25 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698