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.
Read · observe · return to a useful question
Connection Journal
A short collection about names, identity and what a web request actually demonstrates.
This notebook begins with names and follows the question into a few related readings. Each note introduces one distinction, gives an ordinary example and ends with an idea to carry into a small check. Use the index to choose a starting point and return to it when the question changes.
Explore the notebook
Start here
Choose a useful starting point
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.
A route through this collection
The opening reading, keep names and addresses separate, introduces the main question. The next two readings offer different ways to look at it: what a verified connection tells you and read a failure one layer at a time.
Each reading stands on its own and links to its neighbours. Follow the section list to a useful distinction, then return to the index when the question changes. A short record of what you observed will be more useful than reading everything at once.
Choose a note from the full index, or read how this notebook is arranged.