views:

62

answers:

1

I have run into the problem where my css files are being cached in browsers. This is a fairly common problem, and a common solution is to simple add a version number in the url to the css file. Example: MyCSS.css?ver=1.12

However, I'm using a custom skin for DotNetNuke which forces the usage of the file: skin.css

I don't have a way to point browsers to skin.css?ver=1.12 (or at least I'm not aware of a way)

Are there any tricks I can play with IIS, DNN, or ASP.NET (default.aspx file for DNN perhaps?) to force clients to reload CSS?

Thanks. Getting really tired of serving broken content to clients after updates.

+3  A: 

In the IIS Manager, right-click on the file and select Properties. Go to the HTTP Headers tab, tick Enable Content Expiration and set a very low value on your new file.

Chris Cox