My main point was not to _force_ redirects. Overall, having HTTPS is a good thing. The problem creeps up for anyone on older hardware wanting to visit sites. Let them take the risk if they are okay with it. I believe that is a better and more accessible option instead of shutting them out completely.
@tdarb Update: I was browsing my own site which took me to your “Consider disabling HTTPS auto redirects” article again. I navigated to the donation link at the bottom. It took me to an unencrypted HTTP page with payment information. I had to manually edit the URL to HTTPS so I could know the payment info was legit. This was not my first time visiting that page, but it was the first time I noticed the lack of TLS on it.
Though even with an HTTP-HTTPS re-direct in place just for that page, it’d be trivial to intercept the re-direct and act as a malicious TLS-terminating proxy. Or to just edit the donation link destination on an unencrypted page to point to any other interceptable page.
Personally, my approach would be to only list payment info on an HSTS pre-loaded domain (ideally with DNS HTTPS/SVCB records too since I find the idea of shipping a giant list of domains with a UA to be an icky hack) to side-step that issue, at least until “global HTTPS-first” becomes the default behavior in the vast majority of browsers.
@Seirdy Valid points. I will most likely redirect that page to a donation platform directly (skip over crypto entirely) - avoids all those pitfalls
Maybe you don’t care about SEO, but a business sure does.
TLS certificates convey trustworthiness. The appearance of which is just as important as its actuality.
Security is more important than performance, period. Unless you’re operating a web server that needs to serve thousands of requests per second, the performance gain is irrelevant.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.