Say I’ve got a web app. I add some features to it, and those features require additions to some existing CSS files on my web server. I deploy my new features and CSS additions to my server, and they work great. Users visiting the site will probably have cached CSS in their browser, though, which means the new features will look broken/weird until either they manually refresh the page or their cache expires. The problem might be even worse if there’s a cache server between my server and the user, in which case even a manual refresh won’t help (I don’t think).
Is there a common way to avoid this?
EDIT: I’m running on ASP.NET 4.0.
You can add an arbitrary name value pair to the end of your css request and it will act as if it’s not cached. For instance:
When you make a change change the sid value.