I was replying to Kaan, however I think you will be out of luck if you want google to replace the front end infrastructure branding - which has nothing to do with appengine and probably there is no facility to do what you ask. Though it's worth a try ;-)
T On Thursday, October 31, 2013 8:40:08 AM UTC+8, Jason Collins wrote: > > TIm, the point is that I don't want _any_ branding. I realize that I won't > be able to project my application branding through the layers, but I want > Google to replace their branded error screen with a brandless, > black-on-white-text error screen. > > j > > On Wednesday, 30 October 2013 18:02:23 UTC-6, timh wrote: >> >> You need to consider all the layers involved here. >> >> If the errors occur in infrastructure before it even gets to appengine >> (and custom static error pages) then how can you brand the error page, >> and something has to be shown. >> >> T >> >> On Thursday, October 31, 2013 1:23:16 AM UTC+8, Jason Collins wrote: >>> >>> We are getting reports of our customers seeing Google-branded 503 error >>> screens (attached). >>> >>> This is a bad thing and needs to be corrected. Usually there is a >>> non-branded black text on white background error screen for truly >>> catastrophic issues in the serving infrastructure. Where is the >>> Google-branding coming from? >>> >>> Is anyone else seeing this? >>> >>> j >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
