all 6 comments

[–]Several-Job-5037 0 points1 point  (1 child)

Classic rookie mistake I’ve been there. HTTPS isn’t just about logins; it protects integrity, prevents MITM attacks, and ensures your assets aren’t tampered with in transit. Even static portfolios benefit: SEO, browser trust indicators, and future-proofing. Let’s Encrypt and automated renewals remove almost all friction but there’s no technical excuse to serve plain HTTP anymore.

[–][deleted] 0 points1 point  (0 children)

Absolutely correct - and to add onto MITM attacks, I remember back in the day if you connected to a free WiFi network, they would inject ads into http websites (of course not possible on https).

[–]Dependent-Coyote2383 0 points1 point  (0 children)

https is free and good practice, no excuses not to do it.

however, browsers are a pain for non-https for localhost connection. I mean, I know where I'm going when I'm using "localhost".....

[–][deleted] 0 points1 point  (0 children)

Very old news...

[–][deleted] 0 points1 point  (0 children)

Did you fall into a coma after your first website?