HTTPS explained with carrier pigeons โก๏ธ
Cryptography can be a hard subject to understand. Itโs full of mathematical proofs. ๐คท๐ปโโ๏ธ
But unless you are actually developing cryptographic systems, much of that complexity is not necessary to understand what is going on at a high level. ๐
If you opened this article hoping to create the next HTTPS protocol, Iโm sorry to say that pigeons wonโt be enough. ๐
Otherwise, brew some coffee and enjoy the article. โ๏ธ
https://t.me/pgimg/142
[ Article ] : kutt.it/https
ใฐใฐใฐใฐใฐใฐ
#HTTPS #Cryptography
@ProgrammingTip
Cryptography can be a hard subject to understand. Itโs full of mathematical proofs. ๐คท๐ปโโ๏ธ
But unless you are actually developing cryptographic systems, much of that complexity is not necessary to understand what is going on at a high level. ๐
If you opened this article hoping to create the next HTTPS protocol, Iโm sorry to say that pigeons wonโt be enough. ๐
Otherwise, brew some coffee and enjoy the article. โ๏ธ
https://t.me/pgimg/142
[ Article ] : kutt.it/https
ใฐใฐใฐใฐใฐใฐ
#HTTPS #Cryptography
@ProgrammingTip
Telegram
Programming Tips Resources
Add HTTPS To Any Site For Free ๐
Back in the old days, adding HTTPS/SSL/TLS to secure a web site was a big deal. ๐งฎ
You had to spend hundreds of dollars for a certificate, then install it on the web server. ๐ฅ
It had to be specific to the subdomain you were using, or you had to shell out even more bucks for the wildcard cert. And theyโd expire sometimes, and your site would go down, and that was never fun.๐ ๐ปโโ๏ธ
Times have changed.โ๏ธ
Yes, you can still do things the old way, and there are some advantages to doing so.โ๏ธ
But HTTPS is expected now. Google actively penalizes sites that donโt support it. Browsers are quick to tell you about โNot Secureโ sites you visit.โ ๏ธ
So, if you have a smaller site, like a blog, that you want to secure but you havenโt because itโs traditionally been a huge hassle and some expense to support HTTPS, youโre going to love CloudFlare.โจ
[ Article ] : bit.do/frehttps
ใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธ
#HTTPS #SSL #CloudFlare
@ProgrammingTip
Back in the old days, adding HTTPS/SSL/TLS to secure a web site was a big deal. ๐งฎ
You had to spend hundreds of dollars for a certificate, then install it on the web server. ๐ฅ
It had to be specific to the subdomain you were using, or you had to shell out even more bucks for the wildcard cert. And theyโd expire sometimes, and your site would go down, and that was never fun.๐ ๐ปโโ๏ธ
Times have changed.โ๏ธ
Yes, you can still do things the old way, and there are some advantages to doing so.โ๏ธ
But HTTPS is expected now. Google actively penalizes sites that donโt support it. Browsers are quick to tell you about โNot Secureโ sites you visit.โ ๏ธ
So, if you have a smaller site, like a blog, that you want to secure but you havenโt because itโs traditionally been a huge hassle and some expense to support HTTPS, youโre going to love CloudFlare.โจ
[ Article ] : bit.do/frehttps
ใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธใฐ๏ธ
#HTTPS #SSL #CloudFlare
@ProgrammingTip
Telegram
Programming Tips Resources