2

I recently started using AWS Cloudfront to serve my static files with CDN. Since then, when I deploy updated static files such as js or css, CDN doesn't serve updated static files right away. Because of this, Python files (I'm using Django) or HTML files are shown wrong as they were supposed to be working correctly with updated static files.

I found this documentation. It says that I need to add identifier to the static files. For examples, I gotta change functions.js to functions_v1.js every time deploying, so that Cloudfront doesn't serve cached static files, but serve updated static files. I manually changed the updated static files, and it worked well. However, I felt like that 's a hassle and there must be a better way so that I don't need to change all the updated file names one by one manually.

Can anyone give me a direction about this? I'm really confused about that.

Jay
  • 21
  • 2
  • 3
    Everybody does this. – Michael Hampton May 17 '19 at 18:58
  • 1
    omg.. even when they have to change a lot of static files? do they just edit versions manually one by one? I thought there must've been an automated way :( – Jay May 17 '19 at 19:17
  • 1
    There are automated ways - your build tool or development framework can handle it. Django has a number of solutions. https://stackoverflow.com/questions/9130555/django-static-files-versioning – ceejayoz May 17 '19 at 20:46

1 Answers1

1

Everybody does "cache busting", this very page has at least 5 versioned URIs. If you send a header to cache for a year, the browser isn't going to request it again for that long.

With tooling it does not have to be manual. Specifics about implementing this in your favorite content management system or web site generator are more of a topic for a web developer forums.

John Mahowald
  • 32,050
  • 2
  • 19
  • 34