I add an md5 hash of the app version to the css link, so the css is always fresh for a new version. You can not rely on your users to hit ctrl+refresh...
On Wed, Jan 4, 2012 at 11:41 AM, djidjadji <[email protected]> wrote: > I always use the following method when uploading new application code. > > I have two versions of the code: "dev" and "main" > > "main" is the default version. > > I upload the new code to the "dev" version and test if the update is > working by using the url > > http://dev.appname.appspot.com > > Then temporarily make "dev" the default version. > > Upload the code to "main" and make "main" the default. > > This method never failed for static content (css,js). I need to force > reload shift-ctrl-R the page to ignore the browser cache content. > > If you apply a cache buster to your css link your users will see the > updated css immediate. > > <link type="text/css" rel="stylesheet" href="/css/style.css?ver=20120104"> > > You need to change the string anytime you upload a new version. If you > use source version control you can use the version number of the css > file. > > -- > 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. > > -- Pieter Coucke Onthoo BVBA <http://www.onthoo.com/> - zamtam.com <http://www.zamtam.com/> <http://www.zamtam.co.uk/> -- 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.
