In general, you don't want to disable browser cache for elements that should be static in a production environment. (And, really, you don't want to be doing development in a production environment either. In a local dev/test environment, you can globally set all of the cache parameters on your web server to "total amnesia" without incurring any real costs, but on a public-facing server that would be the equivalent of saying "who needs an 8-core Xeon when we have a perfectly good 486SX/25 box lying around?") You do have some real control using .htaccess to set cache-control headers, but that won't help a lot if the asset is already stuck in cache. Locally, you can either force a refresh (Ctrl-F5 twice usually does it in Chrome; Ctrl-F5 once works in most other browsers) or selectively delete your site (and your site only) from your history. In production, one would normally use a versioned file name to ensure that other users get the changes immediately without a refresh.