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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked.html

Issue 319183008: Revert of Implementing mixed content for forms posting to insecure location from secure ones (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Created 6 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("WebKitAllowDisplayingInsecureContent", false) ;
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 window that shows a form with "action" pointing to an insec ure
19 location. We should not trigger a mixed content callback even though the main fr ame in the window is HTTPS and the form is pointing to insecure content, because we've set the preference to block this.</p>
20 <script>
21 window.open("https://127.0.0.1:8443/security/mixedContent/resources/frame-with-i nsecure-formSubmission.html");
22 </script>
23 </body>
24 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698