I'm wondering if I can get some advice on how everyone out there is handling content expiration for e-commerce sites. I'm running into some issues now and then that I think are caused by the user not getting the newly-fixed script files when they come to the site. I have used the querystring method of "file.js?v=123" in some places, but for some includes, it's not practical to change it on every page it's included on. I'm looking into the content expiration settings in IIS, but am wondering the tradeoff of the user having to download the script again for every page. Some of our script files are pretty large, so load-time is a concern. How can I get the best of both worlds where the user can load a cached version but make sure they get the new version as soon as it's uploaded?