I'm trying to wrap my head around client side (web browser) caching and how it works in relation to IIS 7.5 cache control headers.
If we want to force clients to reload cached resources, how must IIS be configured?
Do we need to set expire web content immediately if the resources on the server have a more recent Modified Date (or ETag value)?
Right now we're not setting any cache headers. So if I set a cache header of no-cache (which I think is the equivalent of expire web content immediately) will that force the web browser to obtain a new version of a particular file. Or will the browser only request a new version after it deems its current copy to be stale and then from that point forward not cache it?
Would a best practice be to set a cache control flag of 1 week, then 8 days before I know I am going to make a change set the cache control down to for instance 30 minutes?
But if I do that and then need to immediately expire an item from users caches because there was an issue with it how do I do that?