The latest articles on DEV Community by BmPdDNbK (@bmpddnbk). https://dev.to/bmpddnbk https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3975025%2Ff997e44a-3c29-4e26-b61a-a71ceb732b35.png https://dev.to/bmpddnbk en BmPdDNbK Tue, 09 Jun 2026 02:07:01 +0000 https://dev.to/bmpddnbk/a-crude-workaround-for-fixing-stale-static-asset-caching-3j0h https://dev.to/bmpddnbk/a-crude-workaround-for-fixing-stale-static-asset-caching-3j0h <p>A while back, I used Nginx reverse proxy caching for static files, and found that after deployment, clients were still pulling old files. Later, I used a pretty crude but effective workaround: add a custom query fingerprint to the asset path and change it on every build.<br> I added a line in the CI step to generate a fingerprint, and used this value directly:<br> BUILD_FINGERPRINT=nJ4KUcQ7r621TfaZ3QROayoHHDJdV8Jw<br> Then I used this variable to replace asset_version in the Nginx config (details omitted). On the frontend side, I also changed it to:</p> <p>That completely broke the cache, and even CDN edge nodes would refresh properly.</p> cicd devops frontend webdev