kepstin
I'm kepstin, but trekkier. (recently moved from @kepstin@glitch.social)
I spend most of my time trying to make computers do things that other people want them to do, mostly in Linux. Big fan of Japanese anison, pop, and doujin music. Recently on a bit of a retro-computing bend.
I contribute to the BigBlueButton open source conferencing software (while working for Blindside Networks), I'm a developer on the Exherbo Linux distro, and I sometimes poke information into MusicBrainz.
Ah, turns out when I lost my umbrella, I lost it in a pile of stuff inside my apartment. Anyways, I now have 2 umbrellas. Guess I'll leave the second one in my car or something.
@caten@mathstodon.xyz In upstream Firefox, clicking the "Proceed to…" button saves an exception for that site, meaning you should only ever see this warning once for any given site. I don't believe there is any way to disable this warning in general (doing so would make https certificate validation ineffective).
If you are running a large number of different local sites, you could consider setting up a private certificate authority and adding it to your system trust store (or just Librewolf, depending on use case). The browser should then automatically trust the certs signed by that CA used by your local sites. (If you own a domain name, you could also get "real" free letsencrypt certs for local servers using dns validation).
Regarding the "no https" warning - check what you have the "https only mode" option set to under about:preferences#privacy ? There's also some tweaks in about:config if you search for dom.security.https_only tho I'm not sure what they all do.
Weird things can also happen regarding https if some service has set the Strict-Transport-Security header when you didn't expect it to.
