Bug 142342

Summary:	Ensure mixed content forms are detected
Product:	WebKit	Reporter:	Michael Catanzaro <mcatanzaro>
Component:	WebCore Misc.	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Normal	CC:	mcatanzaro
Priority:	P2
Version:	528+ (Nightly build)
Hardware:	PC
OS:	Linux
Bug Depends on:
Bug Blocks:	140625

Description Michael Catanzaro 2015-03-05 06:50:26 PST

If a form on an https:// page posts its result to an http:// URL we need to make sure we are displaying an insecure content warning. Otherwise there's no way to know when your credit card data is sent in the clear. There is no test for this currently. Add a test and if the test doesn't pass, fix it.

Unfortunately we cannot block this behavior for compatibility reasons (i.e. the form must be treated as "passive" content you "canDisplay" even though it would make more sense to consider it "active" content you "canRun").

Comment 1 Michael Catanzaro 2023-03-03 14:14:07 PST

(In reply to Michael Catanzaro from comment #0)
> Unfortunately we cannot block this behavior for compatibility reasons (i.e.
> the form must be treated as "passive" content you "canDisplay" even though
> it would make more sense to consider it "active" content you "canRun").

Nowadays we want to make sure the request gets upgraded or blocked, whatever the mixed content spec says should happen.