caching - Still seeing old file version after CDN and browser cache purge -


for our project have javascript asset loads onto our page. updated js file frequently, , when deploy purge cdn caches file ensure users served newest file.

recently, have found though purge cdn cache, , purge our local browser cache (for testing), still see old version of file in browser.

here longer list of things we've done try ensure we're covering our bases:

  • we verified correct file deployed checking origin (the s3 url real file lives behind cache) , see correct file there... thumbs up!
  • we verified cdn cache purge worked, accessing file directly @ file's cdn cache url, , see correct file there... thumbs up!
  • we clear our browser cache , load our website, , our updates not there... thumbs down!
  • we in dev tools, find our js file in source/debug tab (tried chrome, firefox, ie, safari, etc), , inspect code find our updates not there... thumbs down!
  • tried in incognito mode (and analogs in respective browsers) , still saw old code... thumbs down!
  • we went far reinstall browsers (chrome , firefox) , blow away saved application data, , when reinstalled, old code still there... thumbs down!
  • we tried booting clean vm image , accessed our website there, , old code still showed in browsers. @ point, no amount of profanity express our frustration. thumbs down.

why browsers find old code when have verified our new code live both in origin , on our cdn, caches have been cleared, browsers reinstalled, , on vms? missing?


Comments

Popular posts from this blog

php - Permission denied. Laravel linux server -

google bigquery - Delta between query execution time and Java query call to finish -

python - Pandas two dataframes multiplication? -