Field Notes

A webrequest

A short guide to DNS, TLS, HTTP and caching, from address bar to screen.

Start reading

Follow the request

Opening a page involves several different jobs. Understanding each job is more useful than memorising the acronyms.

Find the address

DNS

A domain is a name people can read. A browser usually needs address records before it can connect to the service. A resolver checks its cache and, when needed, asks the DNS system.

An A record supplies an IPv4 address; an AAAA record supplies an IPv6 address. Answers normally include a time to live, or TTL, so a record change may take time to appear everywhere.

Name resolution answers “where?”. It does not prove that the service you reach is trustworthy.

Read MDN on domain names

Check the identity

TLS

HTTPS uses TLS to protect data travelling between browser and server. During the handshake, the peers agree on connection parameters, and the browser checks the certificate presented for the name being visited.

The certificate must be valid for the visited name, within its validity period, and pass the client’s trust checks. Ignoring a certificate error removes an important identity check.

An encrypted connection protects the journey. It is not a guarantee about a site’s claims, operator or downloads.

Read MDN on TLS

Ask for a resource

HTTP

HTTP describes how a client asks for a resource and how a server replies. A request includes a method, a target and headers, sometimes with a body. A response carries a status code, headers and, when appropriate, a body.

GET is commonly used to retrieve a resource. A 200 response indicates success; 404 means the target resource was not found. One page often leads to more requests for its styles, scripts and images.

A simplified HTTP/1.1 request
GET /notes HTTP/1.1
Host: example.org
Accept: text/html
Read MDN’s HTTP overview

Reuse a response

Cache

A cache can keep a response for later reuse. Servers communicate caching policy through headers such as Cache-Control. This can avoid repeated transfers, but public resources and personal content need different policies.

no-cache permits storage but requires validation before reuse. no-store instructs caches not to store the response. The names sound similar, yet behave differently. When an update seems missing, inspect the response headers first.

Allow shared caching for one hour
Cache-Control: public, max-age=3600
Read MDN’s caching guide

Read further

These are introductory reading notes. For implementation details, continue with the source documentation and observe real requests in your browser’s developer tools.