What’s up everyone? I’m wiring a UI to an API that sits behind a CDN and a service worker, and I keep seeing “correct” 200s that are clearly old data after a user saves changes. Hard-refresh fixes it, so it smells like caching layers fighting each other, but I can’t just disable caching because performance is already tight.
What’s your practical strategy for making API responses reliably fresh when it matters (writes, immediate reads) while still keeping CDN/browser caching on for the rest?
