wow HTTPS sure makes swapping servers around less fun.
combined with the DNS lag I also have to make sure the certs get moved properly or people will get invalid certs. fun.

part of my problem with modern web development is that OBVIOUSLY everything should be HTTPS and the latest TLS and everything to avoid security issues, but I'm a retrocomputerist and I'm still like "but then my site won't work on Netscape 4.0! ;_;"

@foone@digipres.club I mean I don't necessarily agree that everything should be HTTPS. If you don't handle privacy-related info or user logins... why should it?

@LuigiDev @foone because it hides the host name. Because then things that are sensitive cannot be targeted or forced to downgrade

@falken @LuigiDev @foone The hostname is typically exposed by TLS Server Name Indication, which in turn is required to support per-vhost (as opposed to per-IP-address) certs.

@vjon @LuigiDev @foone false. SNI is part of the encrypted payload in all modern TLS, because of exactly this issue in SSL

@falken @LuigiDev @foone If by “all” you mean “the one latest version, and then only if you don’t advertise any compatibility with any older version”, then yes. :-)

@vjon @LuigiDev @foone death of IE and rise of evergreen browsers with own DNS (including over HTTPS) and networking stacks helps massively with adoption.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.