Mixed content detection triggers on "mailto:" links |
||||||
Issue descriptionI was surfing a web and occasionally noticed that Chrome shows "Mixed content" message because of the following code: <form action="mailto:mail@example.com" method="post"> <input type="submit" value="some value"> </form> The message looks like: Mixed Content: The page at 'https://some_website/' was loaded over a secure connection, but contains a form which targets an insecure endpoint 'mailto:mail@example.com'. This endpoint should be made available over a secure connection. I guess that "mailto:" links should be ignored, but may be I'm wrong.
,
Aug 26 2016
elawrence@: I don't think that argument is trying to justify an edge case that we didn't think about, or where too lazy to address. Chrome sometimes *does* know the protocol handler (e.g. GMail or Inbox). And on the other side of the coin, even an HTTPS form submission may redirect to an HTTP page or be handled on the backend in a way that leaks details. I'm interested in hearing from Mike whether anyone has explicitly thought about this for Chrome.
,
Sep 6 2016
,
Sep 6 2016
1. Max sits next to me, so it's totally important that we fix this one way or another so I can avoid the evil eye. :) 2. I never thought about `mailto:`, no, but I like Eric's retconned justification for the current behavior, if not the current message. So, let's change the message, but keep the UI-degrading behavior? Fewer `mailto:` forms is better `mailto:` forms. Also, I don't like either IE or Firefox's current behavior.
,
Sep 8 2016
Sounds good!
,
Nov 30 2016
,
Nov 10 2017
,
Feb 18 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by elawrence@chromium.org
, Aug 25 2016