Reputation: 30855
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?
Upvotes: 2
Views: 10498
Reputation: 81
When the skin is created "correctly" the skin.css file should (in DNN 6+ I think) include a version QS parameter when it's loaded. The version number is upped when you install a new skin version or you can do this through Host > Host (application) settings > Advanced settings > Client Resource Management > [Increment Version]
Upvotes: 0
Reputation: 631
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.
Upvotes: 2