@makegeneve This would only be for the webpage itself.
I would redirect in Nginx and not on my router. Router would still allow port 80 since I believe it is required for the Twitter API I have to work with as well.
I still have a lot to learn about what I can do specifically without messing anything else up. lol
@makegeneve It's more than an experiment lol. The site is hosted externally as well.
Well... landing page for now lol
@freakinbox I'm sure there's an obscure use case that I can't think of, but in general it's a "no".
It requires a 301 redirect which will delay loading by 1 ping time... but most new traffic will come to https anyway.
@freakinbox @levi If you happen to be into retro hardware/software *and* you want your retro kit to be able to access the site, leaving an HTTP option open makes sense. Modern SSL/TLS standards frequently leave older browsers behind.
On the other hand, if all of your clients are modern hardware with modern browsers and you are comfortable installing certs on the server there isn’t any harm.
@unamanic @freakinbox yeah I guess that's a fair point. I imagine js support would be a more common problem?
I'm sure loads of devs for personal sites and such don't consider backwards compat past the last few major versions