Emma is correct that this is the solution for your problem and we are
aware that it's important for the adoption of HTTPS. We already
implemented the first half to support the upgrade of the form @action
from HTTP to HTTPS in Firefox 41 but bug 667233 is needed to handle the
form's origin being upgraded.
MattN
On 2015-11-25 10:11 AM, Emma Humphries wrote:
I've been reviewing Password Manager bugs the past few days, and the
https/http issue has been bugged:
https://bugzilla.mozilla.org/show_bug.cgi?id=667233 and has recent
activity. It has an owner, and a priority.
On Wed, Nov 25, 2015 at 10:06 AM, Thomas Schäfer
<wollensiedaswirklichloesc...@gmail.com> wrote:
Am Mittwoch, 25. November 2015 19:51:11 UTC+2 schrieb Philipp Wagner:
Am 25.11.2015 um 18:33 schrieb Boris Zbarsky:
On 11/25/15 12:24 PM, Thomas Schäfer wrote:
No, the are stored using the mechanism firefox offers for storing
credentials (Settings -> Security).
So these are HTTP Auth credentials (based on 401 responses from your
server)?
I guess the OP is talking about passwords auto-filled into form fields?
Philipp
Yes. Maybe I didn't made myself clear enough on that point: I am talking about
the auto-filled form fields where the auto-fill works on the non-ssl version of
the page (where they were originally saved) and does not work on the ssl
version of the page including the same form.
Thomas
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
