edit: Maybe this would be better in a different forum (like site administration), but whatever. There's a site in particular I'm having trouble dealing with because of the constant design changes happening. We use SVN locally and on the server, but everytime any kind of interface change is made, most users are still on the old. It seems that one answer is to use: <meta http-equiv='cache-control' content='no-cache'>, which seemingly works... but then no cache is pretty terrible and slows down the speed of the site significantly. Maybe if a developer could load this once per IP or something like that? Not my area, but it sounds like it could work. There has to be a real solution to this in any case. I've heard some folks say to add revision numbers on to the end of changed images, but that isn't going to work for a large site with 60+ AFAIK. Here's the site's significant cache headers: Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Of course images still cache though, so I don't know what all that is for. And if cache-control is already set to no-cache in the headers, I'm confused as to why <meta http-equiv='cache-control' content='no-cache'> made a difference when I tested. Ugh, this is all confusing and reading about it doesn't make it any less so. Thanks, whoever helps.
I use this code in the header. I think this works best with ie. <meta http-equiv="Expires" content="-1"> <meta http-equiv="Pragma" content="no-cache">