4 ms·
They also asked users to import it into the Mozilla store, which (for mostly historically reasons) is separate. Feels like Mozilla should be revoking that speci
by revelation 9y ago
They also asked users to import it into the Mozilla store, which (for mostly historically reasons) is separate. Feels like Mozilla should be revoking that specifically.
Ultimately, I have no idea what they are even trying to achieve here. If this is all localhost communication, HTTPS isn't doing anything.
- mkup 9y agoProbably they're trying to avoid "not secure" warnings from browser which are displayed if http-served web page contains password input fields (Chrome 56+, since October 2017).
- mschuster91 9y agoThese don't appear for localhost, though.
- Xylakant 9y agoIt’s not localhost as domain, it’s a real registered domain that points to the loopback address.
- revelation 9y agoIt should still not show the warning then, right? Because you're still talking to localhost, and that is ultimately what matters. And what is the motivation behind having a domain you need internet for to resolve to point towards localhost to use with a certificate only localhost is meant to have? This is all sorts of effed up.
- netsharc 9y agoI'm guessing it's so the end-users can just say "go to www.[bla].de", similar to going to gmail.com...