this post was submitted on 21 Aug 2025
333 points (99.4% liked)
Technology
74296 readers
4277 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
HTTPS may be the official designation for the port, but it is the de facto standard port for TLS. Whatever you want to send over TLS, doesn't really matter.
HTTPS is just HTTP served over TLS (originally SSL).
Step by step, if you were to analyze a web connection over port 443, you would see that the client first negotiates the TCP connection (via three-way handshake), then TLS, and it's not till after TLS is established that HTTPS is negotiated.
In that way, it's kinda wrong to say it's the HTTPS port. It's really, nowadays, the TLS port. HTTP is just one of many protocols that can ride on top of it, and when we do that, we call it HTTPS.