title: Chrome caching like a mad browser
body: <p>I've got a web service that, like most others, uses js and css files.  I use the old trick of appending a version number to the js and css file like; ?v=123 and that gets changed every time we update the service on production.</p>
  
  <p>Now, this works fine on all browsers, except for Chrome.  Chrome seems to prefer it's cached version over getting the new one and therefor seems to ignore the appended variable.  In some cases, forcing it to refresh cache (cmd+r / ctrl+f5) wasn't enough so I had to go into options and clear out the cache for it to load up the new content.</p>
  
  <p>Has anyone experienced this issue with Chrome?  And if so, what was the resolution to the problem?</p>