https://abbreviatory.com/tags/http/ Recent content in http on Abbreviatory.com Hugo -- gohugo.io en-us Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Test runs and logs aren’t the only big outputs a coding agent reads. It reads diffs all day, to review what it changed. It calls APIs with curl and gets back a wall of JSON. It runs find to see what’s in a repository, and gets ten thousand paths. Abbreviatory v0.4.0 reads all three. Each one gets rules of its own, because each one has its own idea of what matters. https://abbreviatory.com/how-to-watch-an-api-for-new-errors-with-curl-and-run-history/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-to-watch-an-api-for-new-errors-with-curl-and-run-history/ Plenty of APIs answer 200 OK and put the trouble in the body. A catalogue export says "status": "partial", and three of its 2,500 items carry an error object saying the price feed is stale. The status code says all is well, and the 720 kB of JSON is too much to read every time someone checks. The response in this example is the catalogue export from our test fixtures, fetched with curl -si from a local server: 37,534 lines with the headers.