Keep names and addresses separate
A name is a durable label. An address is one answer about where to try a connection. Treating them as separate observations makes a problem easier to describe.
Names, paths & everyday questions
Connection Notes
A small reference on names, connections and the boundaries between them.
A page opens, a name resolves, a request takes longer than expected. These ordinary events contain several different questions. This notebook separates them into short, practical readings, so an observation can become something more useful than a guess.
Explore the notebook
Start here
Follow one question at a time
What a verified connection tells you
A certificate check connects a secure session to the requested name. The page returned inside that session still deserves its own review.
Delay and throughput answer different questions
A quick first reply and a fast transfer describe different parts of an experience. A single number cannot stand in for both.
Read from the boundary you can see
Start with names if an address seems unexpected, or identity if a secure connection reports a warning. For a page that loads slowly, the notes on latency and request budgets offer two different ways to look at time.
The readings are intentionally small. None depends on a particular product, network operator or account. Keep a useful explanation, try one modest check, and return to the index when the question changes.
Choose a note from the full index, or read how this notebook is arranged.