ป้องกันแคชด้วยเวอร์ชันไฟล์

Browsers save assets to load pages faster. That is great until you ship a new style.css and visitors keep seeing the cached old one. 🗂️

If the URL stays /static/style.css forever, the browser assumes nothing changed. Your fresh design simply never reaches the user.

The fix is cache busting: change the asset URL whenever the file changes. A new URL forces the browser to download again.

The simplest trick adds a version query parameter. /static/style.css?v=2 is treated as a new resource by the browser.

Each time you deploy changed CSS, raise the v number. A central variable beats editing the value in many templates by hand.

A smarter bust uses the file modification time. Read getmtime so the version changes only when the file actually does.

Any unknown keyword you pass url_for becomes a query parameter, so you can attach a computed version cleanly.

The strongest approach names files by a hash of their contents, like style.abc123.css. New contents mean a new name and a guaranteed refetch.

Because a hashed name only changes when contents change, you can cache it almost forever. Speed and freshness stop fighting each other.

Asset bundlers generate hashed filenames and a manifest mapping logical names to hashed ones, so your templates ask for the current build.

Start with a simple ?v= version for small projects. Move to content hashes once a build pipeline is worth the setup.

Why does adding ?v=2 to an asset URL make the browser fetch a fresh copy?

You learned to change asset URLs so browsers refetch updates: a version query for small apps, content hashes for serious builds. 🚀