IIS6/7 Doesn't enable HTTP Response Headers for content expiration/caching by default?
- by Jerry Mayers
I just realized that by default when you create a new site in IIS it defaults to not including any expiration headers. I had been assuming it would be enabled with something reasonable like a day or so. Is this truly the default? Is there anyway to change to a default policy that keeps expiration/caching enabled?