I checked and noticed the following files as having no expiration date. jquery-ui.css groups_logo_sm.gif rpx.js
These files have a date and are set to 90-days, chrome is suggesting a year. base.css calendar.css ptjq.pkg.js peertool.js background.gif header.gif menu.gif question32.png agplv3-88x31.png If you want to change the date on these to a year just change "90d" to "1y" or any other time period you would like. The missing expiration date on the first three files is interesting though. I checked with firebug and indeed they have no expiration date, though reloading the page in firefox is not downloading any of those files that might not be true for all browsers. Are you possibly serving some of those files as URL references from the style sheet? Are any of those files *not* served from the /static folder? On Sep 14, 3:43 pm, Michael Ellis <[email protected]> wrote: > When I analyze the network performance of my GAE hosted > application,http://peertool.appspot.com with Chrome Dev Tools Audit, the top > listed suggestion for improvement is "Leverage browser caching", viz. > > """ > The following resources are missing a cache expiration. Resources that > do not specify an expiration may not be cached by browsers: > jquery-ui.css > base.css > calendar.css > ptjq.pkg.js > peertool.js > background.gif > groups_logo_sm.gif > rpx.js > header.gif > menu.gif > question32.png > agplv3-88x31.png > """ > > Most, but not all, of these are served from the static/ directory. > > I checked app.yaml and found that it has the settings recommended in > an earlier thread on this group: > > """ > - url: /(?P<a>.+?)/static/(?P<b>.+) > static_files: applications/\1/static/\2 > upload: applications/(.+?)/static/(.+) > secure: optional > expiration: "90d" > """ > > I'm using web2py version 1.84.0 (2010-08-28 09:58:51) > > Is there something more I need to do? > > Thanks, > Mike
