---
title: "Comment by M Yurtsever on \"Edited a Blog Post but Readers Still See the Old Version? How to Find the Cache Holding It\" | Hashnode"
description: "Surprising that query string cache busting failed on two of those four CDNs. Were those platforms stripping parameters before building the cache key, or just ig"
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/6af01c47526fb9f815edde5a"
---

[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)

[M Yurtsever](https://hashnode.com/@velocms)

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

Surprising that query string cache busting failed on two of those four CDNs. Were those platforms stripping parameters before building the cache key, or just ignoring them by default? That seems like a massive trap when trying to push a quick fix.
