3 ms·
The death of HTTP/1.1. I posted a link to an article on an HTTP-only website a few days ago, and it was flagged within half an hour because browsers want HTTPS
by sam_lowry_ 4mo ago
The death of HTTP/1.1.
I posted a link to an article on an HTTP-only website a few days ago, and it was flagged within half an hour because browsers want HTTPS.
I know all about JS injection into unencrypted HTTP trafic, but this is beyond the point.
The point is, I can not just spawn a website and make it available to the world from anywhere having only a network connection.
- chadgpt3 4mo agoSure you can, just have to install certbot.
- sam_lowry_ 4mo agoI would rather use acme.sh and ZeroSSL for CA, but that's exactly the problem. Why do I have to beg someone for a proof of nothing just to share a random thought?
- thedevilslawyer 4mo agoThis isn't the thread for it. But setting up a simple protocol or using one of the free dozen CDN static hosting isn't begging.
- chadgpt3 4mo agoIt's not a beg. Them providing this for free is causal to it being required. No free certs would mean no warnings for not having a cert. You "beg" your domain registrar harder.