Thanks for the suggestion but I am already setting the expiry header in the appengine-web.xml file.
As part of my built script I rename static resources with an MD5 hash as part of the file name and set the expires header for a year in the future. These MD5'ed files are being served to my england location from the ip address 74.125.77.121 which geolocation websites suggest is in California. Is california the closest google datacenter to England? On Oct 22, 11:09 am, "Nick Johnson (Google)" <[email protected]> wrote: > Hi, > If you set an expiration time for your static content, it may be cached at > geographically diverse endpoints. Without one, it won't be, as it doesn't > know how long it's safe to cache for. > > http://code.google.com/appengine/docs/python/config/appconfig.html#St... > > *-Nick Johnson > * > > On Wed, Oct 21, 2009 at 2:44 PM, stumpy <[email protected]> wrote: > > > I am developing an application that targets the UK market and am > > looking at ways of improving the download speed of static files hosted > > on app engine such as .js, .css, .png etc. > > > My testing suggests that app engine is serving all static content from > > america which adds significant latency. Downloading a static file of > > size <1KB takes 200-250ms from england. > > > Are there any plans in the future to geographically distribute static > > content across data centers? Or would I be better off using amazon > > cloud front for serving everything static? > > -- > Nick Johnson, Developer Programs Engineer, App Engine > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
