13 docs tagged with "networking"

This page discusses how to view a local development site on a physical phone using IP addresses, and explores solutions for accessing the development environment from public networks, including tunneling services and VPNs.

Load balancing is about deciding where to send the next request. From weighted round robin to response-time aware routing to consistent hashing at L4 or L7, each strategy has trade-offs in complexity, fairness, and statefulness. This guide walks through the common approaches and key design considerations.

A practical introduction to what DHCP actually provides, how a client obtains its network configuration, and what an IP address lease really means.

www was never special — it's an ordinary hostname that happens to be famous. I found out none of my own sites answer to it, which turned a terminology question into a reason to build a scanner.

A practical mental model for distinguishing forward proxies, reverse proxies, gateways, routers, tunnels, and ordinary application dependencies by examining boundaries, control, and point of view.

A deep dive into how a network packet travels from the NIC through DMA, the RX ring, interrupt handling, the Linux network stack, and finally to a user-space application.

Four more domains, same missing www. Every certificate already covered it and every distribution already accepted it — only the DNS record was absent. Nothing in AWS reports that state, because no single service can see it.

A curl-first explanation of how Let’s Encrypt issues certificates, how clients later verify them, and why certificate issuance must be separated from TLS usage.

www.csv-helper.com returned NXDOMAIN for years. The certificate already covered it and CloudFront already accepted it — every part of the fix was done except the DNS record. Then I swept the account and found four more exactly like it.

A map of everything that happens between bytes arriving on a network card and a populated request object in your handler — the phases, the boundaries between them, and what each boundary destroys.

Trace the early web history of client-side proxies, caching, firewalls, and server-side accelerators to understand how the term reverse proxy emerged and why the name still causes confusion.

Every modern host hands you a hostname and tells you to CNAME to it — which is exactly the one thing your bare domain cannot do. The rule is one sentence from 1987, and everything since has been a workaround.

Open working notes for a Go scanner that classifies www support across a domain corpus — corpus sourcing, positional storage, trend methodology, and where the throughput is expected to give out.