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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-formSubmission-in-main-frame-blocked-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 unified diff | Download patch
OLDNEW
(Empty)
1 CONSOLE ERROR: line 2: [blocked] The page at 'https://127.0.0.1:8443/security/mi xedContent/resources/frame-with-insecure-formSubmission.html' was loaded over HT TPS, but is submitting data to an insecure location at 'http://127.0.0.1:8080/se curity/resources/boring.html': this content should also be submitted over HTTPS.
2
3 This test opens a window that shows a form with "action" pointing to an insecure location. We should not trigger a mixed content callback even though the main f rame in the window is HTTPS and the form is pointing to insecure content, becaus e we've set the preference to block this.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698