Learn / Walkthrough

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.

  1. Everything in the open

    Packet 6

    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.

  2. The reply is readable too

    Packet 7

    The server's answer, including the page content, is plain text.

  3. Starting encryption

    Packet 15

    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.

  4. Agreeing on encryption

    Packet 16

    The server picks TLS 1.3. From this point on, everything is encrypted.

  5. The request is hidden

    Packet 20

    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.

  6. So is the reply

    Packet 21

    Only the size and timing of the reply are visible.