TCP to HTTPS, one request under a microscope · check

Know Open, secure and reuse a connection already?

One question for each of the 4 puzzles in this module. A right answer marks that puzzle as passed, so you can jump ahead. A wrong one tells you which puzzle to start with. Nothing is sent anywhere: it's saved in this browser.

Puzzle 0: Why TCP starts with three messages

The third message is lost and nothing else arrives. What is the server missing?

Right. Keep track of what each peer has actually received.

Not quite. The server chose its own starting number before sending SYN-ACK. Learn it in puzzle 0 →

Not quite. The server already received that number in SYN. Learn it in puzzle 0 →

Puzzle 1: Where do the missing bytes go?

The receiver has bytes 101–104 and 109–112. What cumulative acknowledgment can it send?

Not quite. The value names the missing position rather than the latest arrival. Learn it in puzzle 1 →

Not quite. The cumulative value cannot cross a gap. Learn it in puzzle 1 →

Right. Find the first hole after the contiguous prefix.

Puzzle 2: Who proves the server’s identity?

The peer proves it owns a key for images.example.com. The phone asked for api.example.com. What fails?

Not quite. The TCP setup can succeed regardless of the name. Learn it in puzzle 2 →

Right. Key ownership and the intended name are distinct checks.

Not quite. Possession of that other service’s key can still be proved. Learn it in puzzle 2 →

Puzzle 3: Where did the extra round trips go?

On this model, the RTT rises to 100 ms. What is the approximate first-byte time over a fresh connection?

Not quite. The regular request still adds another trip. Learn it in puzzle 3 →

Right. Count dependencies before calculating time.

Not quite. The setup exchanges happen before the regular request. Learn it in puzzle 3 →

Back to the overview →