HTTP compared with HTTPS
This capture asks for an account page twice: once over plain HTTP and once over HTTPS. Compare what an observer on the network can see.
-
Everything in the open
Over HTTP, the request line is readable: the path /account?user=sam and the host name are visible to anyone on the path.
Think about it: What could someone on the same Wi-Fi learn from this packet?
The site, the exact page requested, and the user name in the address. Over HTTP they could also read the reply.
-
The reply is readable too
The server's answer, including the page content, is plain text.
-
Starting encryption
Over HTTPS, the laptop first sends a TLS Client Hello. The server name (SNI) is still visible here, so an observer knows which site you're visiting.
-
Agreeing on encryption
The server picks TLS 1.3. From this point on, everything is encrypted.
-
The request is hidden
This packet carries the same kind of request, but it's encrypted. The path, user name, and headers can't be read.
Think about it: What can an observer still learn from encrypted traffic?
Who is talking to whom, when, and roughly how much data is sent. Not what's inside.
-
So is the reply
Only the size and timing of the reply are visible.