
The cache that froze the cover: when a rename becomes a contract change
Swapping the image at the same path changes nothing for anyone who already downloaded it. The filename now carries a content hash, and two consumers broke instantly.
6 posts

Swapping the image at the same path changes nothing for anyone who already downloaded it. The filename now carries a content hash, and two consumers broke instantly.

13 cross links, zero with UTM: the portfolio's measurement arrived without knowing who sent it, and the fix was a 59-line helper that tags every exit.

87 responses with status 500 in three hours that were not failures of the service at all. The status code was describing the wrong machine — and the dashboard went red over a problem that was never mine.

Every contact form submission in production returned an error, and the form code was fine. Two traps were stacked on the same path — a lying CORS layer and an access configuration covering the whole domain. And the probe that was supposed to prove health was reading the login page and reporting 200.

A normalization rule at the edge layer was replacing the whole site's security policy with a two-line version, and only a test that hit real production noticed.

Two machines, the same code, the same key. One got 200, the other took a 403 with error code: 1010. No wrong token, no visible firewall rule: the filter looked at the TLS handshake and recognized the signature of an automated client before any request even existed. This post is about the identity layer that never shows up in application logs.