IIS and content caching
- by JayC
I'm a web developer and administer of a Windows 2008R2 Could Instance with IIS 7. I recently made an update to our website, but when I revisited the website, the website was being viewed with old stylings. I did a refresh (shift + reload button in Firefox) and of course the website displayed as it should. I didn't worry about it, until my client had the same issue in Safari.
So, my question, in general, is, how do I prevent this from happening again, and yet still afford some caching of our site?
I noticed we did not have content expiration set up on our webserver sites, so I've set that up, but did I really need to?
I've also looked at Etags, and, honestly, it's hard for me to know whether or not I should use them or not. One comment I read somewhere there isn't really any issue with Etags scenarios in IIS (even in webfarms)... but, I dunno.
Anybody have any suggestions, links, info? Thanks.