5d ago · 12 min read · In a previous post we followed a request from your browser all the way to a server's front door. DNS translated the domain name, TCP opened the connection, and the request arrived. But we never looked
Join discussion
Mar 4 · 5 min read · Caching is one of the highest-leverage performance optimizations available — and one of the most commonly misconfigured. A correct caching strategy means returning content instantly from a cache that's close to the user, dramatically reducing latency...
Join discussionMar 3 · 11 min read · Network Debugging Tools: mitmproxy, Charles, Fiddler, and Wireshark Every developer eventually hits a bug where the problem is "somewhere in the network." The API returns unexpected data, but only in production. The mobile app works on WiFi but fails...
Join discussionMar 3 · 9 min read · Hurl: Run and Test HTTP Requests from Plain Text Testing HTTP APIs often means juggling between GUI clients, writing verbose test scripts, or maintaining brittle curl commands stitched together with shell scripts. Hurl takes an entirely different ap...
Join discussionMar 3 · 6 min read · DNS and Networking Tools Every Developer Should Know DNS misconfiguration is behind a surprising number of production incidents. An API call that worked yesterday fails today because a DNS record changed, a certificate expired, or a CDN edge node is ...
Join discussionFeb 26 · 7 min read · Every HTTP request your browser makes includes a header that tells the server who's asking. It looks something like this: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 That string — th...
Join discussion
