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.
The complete index
Notes
A short collection about names, identity and what a web request actually demonstrates.
Begin with any of these seven notes. The section list and neighbouring readings offer a route back when a question changes.
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.
Read a failure one layer at a time
A connection can fail before a name is resolved, during a secure handshake or after a request arrives. Naming the layer narrows the next check.
Why a refresh can show an older page
A browser may reuse stored content instead of transferring it again. A refresh is therefore an observation about both the website and the browser's local state.
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.
Leave a connection check easy to repeat
A short record of the question, conditions and result is usually more reusable than a large collection of unexplained output.
Keep a useful observation
A useful observation begins with a small question. Decide which result would help answer it before choosing what to collect.