*Richard Watson's *post was money.. ackkk.. someone unwittingly let the cache-control header slip into a base request handler.. thnx everyone..
On Sunday, April 29, 2012 12:53:15 AM UTC-7, Richard Watson wrote: > > What if Gregory put (e.g.) Cloudflare in front of the app and used it to > fetch "app" requests and serve them as "www" (I assume that's possible). > This way, people continue to see www and can add www links. Can try it as > a short-term solution while you tinker with the setup and/or wait for the > edge cache to sort itself out. > > It's quite possible that Google's edge cache caches for a maximum period > shorter than a year due to demand/bandwidth priorities, so maybe this'll be > solved in a week or month. > > On Saturday, April 28, 2012 10:13:26 AM UTC+2, alex wrote: >> >> I think you can actually do it without manual intervention from Google >> internally: >> >> Let's say your app (with cached blank page) is currently accessible as >> www.example.org >> >> 1. make sure you remove "cache-control: public ..." headers from the >> response >> 2. add a mapping that will make your app accessible as app.example.org >> 3. like Joshua suggested, change www CNAME into www A DNS record pointing >> somewhere else, where you do a simple (maybe even permanent) redirect to >> app.example.org >> >> Even though it seems like your blank page is cached for a long time now, >> www DNS record will expire sooner (normally 24 ours if you haven't changed >> TTL) >> >> Hope that helps. >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/llofFYky_t8J. 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.
