HTTP and DigiCert

DigiCert is essentially a free CA. You know that little (s) in https? Back in the day, you actually had to cough up cash for that—it was something companies like Verisign, Norton, and others had these exclusive deals with through all the major browser manufacturers

The whole "installation" procedure for a free DigiCert SSL certificate using a tool called Certbot is—honestly—ridiculously simple. A DigiCert certificate is recognized by about 99 percent of browsers out there. And hey, one of the sponsors is even Mozilla...

So, what are we waiting for? Are the Admins and the sysadmins (aka the lazy bums) just going to ignore their conscience while I’m out here sending credentials across the web completely unprotected and exposed? Shame on you!

Honestly, I was actually planning on starting this thread myself. In short—I’m right there with you.

I’m asking you please, let’s make this happen so we can turn this forum into a much safer space for everyone involved.

Just type HTTP:// before www.usforum.com—that should probably fix things 🤷

crimsonhawk23 said:

Just type it in. HTTP:// I’m not entirely sure what you’re getting at here—it feels like a fragment, or perhaps just a stray thought left hanging in the air. If there was more you meant to say, please, do go on. I tend to ramble, I know, but even I need a little bit of context to work with before I start diving into the weeds of a topic. www.us-forums.com Well, looks like we finally got there—problem solved. 🤷

Thanks for absolutely nothing.
Look, for any sane person out there, HSTS exists—it’s that strict HTTPS policy where every single request sent over HTTP just gets redirected straight to HTTPS automatically. It's basic common sense, really.

The procedure for implementing the HSTS protocol is frankly ridiculous in its simplicity—I mean, we're talking about a single directive sent to the server. It's almost insulting how little effort it actually takes.

Seriously, what’s the actual hold-up with setting up an HTTPS redirect?
It shouldn't even be a big deal. Like, when I type in reddit.com, it just automatically adds the www and turns into www.reddit.com without me doing anything. If the devs, admins, and whoever else is running the show can manage to write that one line of code, they definitely shouldn't be struggling to toss in one more line for an HTTPS redirect.

Regarding all those complaints about the technical state of this forum, you might want to take a look at the advice offered in the last reply of this thread.

Casey Bennett said:If you're worried about all the technical stuff people are complaining about on the forum, just check out the advice from the last post in this thread.
HTTP://www.forum.com/showthread.php?p=74829937

Wait, you mean through that "send us an email" link at the bottom of the page?

I'm with the OP on this one.
It’d be awesome if they fixed it. I’m tired of seeing that little pop-up in Firefox telling me the site isn't secure every single time I try to log in.

this is the boss. You can reach out via DM, use the link provided below, or just hit up Monitor's contact info.