There’s theory and there’s practice. Many things are easier to know if theory and more difficult to put into practice.
Using HTTPS, SSL and TLS (HyperText Transport Protocol Secure, Secure Sockets Layer, and Transport Layer Security if you like your acronyms spelled out) seems fine in theory. Getting this website to use HTTPS by default is proving more difficult in practice than I expected in theory.
Humility is good for the soul. This is building character. This is really annoying me.
While I figure it out, here’s some external website links I found useful:
- What is HTTPS? from Cloudflare – https://www.cloudflare.com/learning/ssl/what-is-https/
- What is HTTPS? from SSL.com – https://www.ssl.com/faqs/what-is-https/
- Homepage for Let’s Encrypt, “a non-profit Certificate Authority providing TLS certificates” – https://letsencrypt.org/
- Explanation of HTTPS Everywhere browser add-on from the Electronic Frontier Foundation – https://www.eff.org/https-everywhere
- What is HTTPS? from Semrush, an “online visibility management and content marketing” platform – https://www.semrush.com/blog/what-is-https/
- What is HTTPS? from Fortinet, a networking security company – https://www.fortinet.com/resources/cyberglossary/what-is-https
- What is HTTPS and Why Should I Care? from HowToGeek – https://www.howtogeek.com/181767/htg-explains-what-is-https-and-why-should-i-care/
- What is HTTPS? A Guide to Secure On-Site Experience for Marketers, from SearchEngineJournal.com – https://www.searchenginejournal.com/https-for-marketers/417561/
- What is SSL, TLS and HTTPS? from Digicert – https://www.websecurity.digicert.com/security-topics/what-is-ssl-tls-https
When I look up information on how something works or why I should use it, I try to look up information from people who’ve designed it, who sell it, and who use it.
Someone non-technical explaining something to non-technical audience who “just wants it to work” will often have information and perspectives which a more technical writer won’t think to mention.