Index: LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked-expected.txt |
new file mode 100644 |
index 0000000000000000000000000000000000000000..c472fbfa877b51b32baad4c1d4f94de82d8757bb |
--- /dev/null |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked-expected.txt |
@@ -0,0 +1,3 @@ |
+CONSOLE ERROR: line 3: [blocked] The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-formSubmission.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/security/resources/boring.html': this content should also be loaded over HTTPS. |
+ |
+This test opens a window that show a form with "action" pointing to insecure location. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and the form is pointing to insecure content, because we've set the preference to block this. |