Almost every website is using HTTPS now. If it's not, Google flags it with a nasty looking "not secure" symbol in the left corner. There are a bunc...
For further actions, you may consider blocking this person and/or reporting abuse
One downside that people keep on overlooking: HTTPS everywhere makes for a bad experience for caching proxy servers, which are absolutely necessary for folks with limited Internet access in various parts of the world. Obviously you do want to provide HTTPS everywhere you can, but unless the site is handling user logins or private data, at least provide the option of still accessing via HTTP.
Obviously HTTPS should be the preferred transport, but not everything needs it to be mandatory.
One thing worth noting, if you use a service like CloudFlare, they will provide you an SSL certificate.
I use Let's Encrypt in a lot of places, but my personal site uses the CloudFlare certificate. It's very straight forward and only requires some DNS changes.
That sounds logical, but it's not what happens in real world conditions - try httpvshttps.com/ for a demonstration. There's a good write-up of this on Troy Hunt's blog.
LetsEncrypt have revoked around 3 million certs last night due to a bug that they found. Are you impacted by this, Check out ?
DevTo
[+] dev.to/dineshrathee12/letsencrypt-...
GitHub
[+] github.com/dineshrathee12/Let-s-En...
LetsEncryptCommunity
[+] community.letsencrypt.org/t/letsen...
I believe Netlify also provides a free https whish is incredibly handy.
Excellent article Milecia. For additional reading check out my articles as well. I did a couple awhile back comparing the speed between HTTP and HTTPS + HTTP/2.
Hello!
Thank you for the information. I talked about your article in a LinkedIn post here:
linkedin.com/feed/update/urn:li:ac...
Thanks for sharing Islam!