---
title: "Comment by CDN Edge Ops on \"Edited a Blog Post but Readers Still See the Old Version? How to Find the Cache Holding It\" | Hashnode"
description: "Good write-up on the stale-content trap. The part teams miss is that \"CDN cache\" and \"browser cache\" fail in different ways. A purge that only hits the edge sti"
url: "https://hashnode.com/posts/edited-a-blog-post-but-readers-still-see-the-old-version-how-to-find-the-cache-holding-it/6ad701230af263cdd6a7b238/comment/6ae552c931e61ebcdc8f28aa"
---

[Discussion](https://hashnode.com/posts/edited-a-blog-post-but-readers-still-see-the-old-version-how-to-find-the-cache-holding-it/6ad701230af263cdd6a7b238)

Comment [Edited a Blog Post but Readers Still See the Old Version? How to Find the Cache Holding It](https://hashnode.com/posts/edited-a-blog-post-but-readers-still-see-the-old-version-how-to-find-the-cache-holding-it/6ad701230af263cdd6a7b238)

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Oct 31](https://hashnode.com/posts/edited-a-blog-post-but-readers-still-see-the-old-version-how-to-find-the-cache-holding-it/6ad701230af263cdd6a7b238/comment/6ae552c931e61ebcdc8f28aa)

Good write-up on the stale-content trap. The part teams miss is that "CDN cache" and "browser cache" fail in different ways. A purge that only hits the edge still leaves Cache-Control / ETag on the origin response, so returning visitors keep the old HTML or asset until their local max-age ends. When I chase this I check three layers in order: (1) origin Last-Modified/ETag after the edit, (2) whether the CDN actually received a purge for that exact path (and any hashed asset URLs the HTML points to), (3) response headers in an Incognito window vs a normal one. Versioned filenames or a short max-age on HTML with longer cache on fingerprinted static files usually beats hoping users hard-refresh. Also watch intermediate proxies and service workers — they can keep serving an old shell even when the edge is fresh.
