The Guys at Google offered to Alias these for me, but I instead built an app that does 301's to a new URL. I'll test it for a while before I make the source public, but if you are in need of this app shoot me a note and I'll share it. After it has baked for a week, and I have done some calculations on how many redirects you can serve with a free app.
Aliasing is nice and all, but I wanted to be able to turn things off and on when I needed or to bring back an App Name if I needed later. If I had built my apps correctly a long while ago this wouldn't have been an issue, but I wasn't good about making sure that the Appspot.com url didn't appear in search. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz Sent: Wednesday, November 16, 2011 1:41 PM To: google-appengine@googlegroups.com Subject: [google-appengine] "Redirect" Dead Apps? Upgrades to the way some of my apps works have allowed me to do multi-tenant better than I used to, and so I am looking to consolidate Apps. I can do this with 301's but that requires that I leave the apps running/enabled. I guess what I'm really asking is.. Should I just put up an app that 301's all requests to the "new" app. Or is there a way Google would prefer I end of life and forward Apps? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
