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

Unified Diff: LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-expected.txt

Issue 311033003: 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: Fixed the error when action attribute is empty. 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 side-by-side diff with in-line comments
Download patch
Index: LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-expected.txt
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..de89033bf75bc0ec18b2f1951f9351c8cbfbe8cd
--- /dev/null
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-expected.txt
@@ -0,0 +1,3 @@
+CONSOLE WARNING: line 2: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-formSubmission.html' was loaded over HTTPS, but is submitting data to an insecure location at 'http://127.0.0.1:8080/security/resources/boring.html': this content should also be submitted over HTTPS.
+
+This test opens a window that shows a form with "action" pointing to an insecure location. We should trigger a mixed content callback because the main frame in the window is HTTPS but is posting to insecure location.

Powered by Google App Engine
This is Rietveld 408576698