![]() ![]() These involve changing the request URI for the static resources. The solution is called cache-busting, and there are a number of similiar approaches. Adding the (relatively new) default_expiration and expiration directives to your app.yaml file will achieve the first part of this requirement:īehind the scenes, these directives add additional headers to the HTTP response, letting the browser know that they can safely serve these files from cache on subsequent requests.īut how do we tell the end user browser when our static resources have changed? Ideally, we would like the end user's browser to use its cache for every static resource, on every request, until that resource changes because we have deployed a new application version. In this post I want to share how I think I have achieved this Google App Engine (Python). Arguably a bigger win for the end user experience is to ensure the caching of all of your website static resources (JavaScript, stylesheets and images) is properly optimised. In a couple of previous posts I discussed using Google Closure JavaScript Compiler in your build process to minimise the size of your JavaScript resources. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |