The second part of our series was about caching headers - and in the pro tip about strong vs. weak ETags we briefly teased that strong ETags have a second job: They protect you from lost updates when writing. That’s exactly what today is about.

In the first part of our series, we looked at QUERY, the first new HTTP method in 15 years. Today we’re talking about something you probably use every day without really understanding what you’re doing with it: caching headers.

You are currently working on a feature. Claude Code is running in your terminal, in the middle of a major refactoring. Then you notice a critical bug in production that you need to fix immediately. What now?