If you enable billing, and set caching headers, then yes your files can be cached by the edge servers.
But if you enabling caching headers anyway, the files can be cached by the browsers cache anyway. Which will also delay their 'appearance' The best idea for assets like that is to ensure the URL changes when the file itself changes. Can build this into a build system. Or can just setup it up to automatically use the application version in the url of static files. Can get the current version from the enviroment in code, and then use app.yaml to make urls that include the version number map to single files. On 26 February 2011 21:54, c h <[email protected]> wrote: > Hi, > > I noticed several times in the last week where I updated static files that > are included with my applications, and then when i make my new application > version the default that it continues to serve the old files. It's like the > cache of static files is not being updated when i switch default versions. > If i use the long version-specific URL i get the proper versions of the > files. This is especially troublesome when deploying updated/new webpages > and old CSS is served, making the site un-usable until the cache clears. > Has something changed? do i need to somehow reset my static file cache when > i change default versions? > > Thanks, > > Christian > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
