I've looked at the following link to better understand Sitefinity's client cache settings and after creating my own client cache profile and setting it as the default under System > Output Cache Settings -- Default Client Cache Profile I noticed that it has zero impact on JS or CSS files.
Next I found an article on Falafel about setting the cache control max age in the web.config.
In theory this translates into a client cache setting of one day, or 24 hours, or 86400 seconds. Interestingly though, this setting is not applied to all files. The following lists a file along with the max-age in parenthesis:
In fact, NONE of our custom CSS files in the Global folder of the theme have a max-age set, but looking at Firebug it does have an Expires value of roughly 2 weeks from today.
So the question is: What's the point of the Client Cache settings in Sitefinity and why does the web.config file setting only apply to Sitefinity assets?
It would seem that my first comment applies mostly to CSS files, whereas with JS files it seems to be different. Looking at JS files I see the following:
All of our custom js files (those not coming from Sitefinity) share the same cache settings as the Global.js in the list above.