https://arran4.github.io/blog/tags/caching/Recent content in caching on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Thu, 27 Aug 2026 13:38:30 +0000https://arran4.github.io/blog/post/2026/039-asset-hashing-in-go/Thu, 27 Aug 2026 13:38:30 +0000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/039-asset-hashing-in-go/When building web applications, a common goal is to serve static assets (CSS, JavaScript, images, WASM) as quickly as possible. The most effective way to achieve this is aggressive HTTP caching. However, aggressive caching introduces a challenge: when you update an asset and deploy the new version, you must ensure that users receive the updated file rather than a stale, cached copy, while avoiding unnecessary downloads for unchanged assets. The solution to this problem is asset fingerprinting (or content hashing).