One backup is to use Cloudflare.com for the SSL, which allows you to set rules up in a fine-grained way. It adds a bit of complexity to your stack but should get you running within a couple hours, and then you can wait for GAE to help with this.
Personally if it was for a bank app, even a pilot, I'd pay the $500 for support since it'll likely cost you more to work around the problem. On Thursday, October 25, 2012 9:50:16 AM UTC+2, Jan Killian wrote: > > Hi fellow appengine developers, > > we have a major impact issue on an european bank application, which is > their first Google Apps and Google Cloud experience. We'd need this to be > addressed to keep the trust that Google can provide the service. Is there > any option to get such a major issues fixed in a reasonable time? > Preferably other than paying for a premier account, which is not needed for > this pilot product at this time. > > The issue was already reported on appengine public issue tracker for over > a month: http://code.google.com/p/googleappengine/issues/detail?id=7979 > > App Engine returns 403 on http://customdomain, instead of redirecting it > to https, when secure:always is set in app.yaml. Authentication for the > application is set to Google Apps domain, which may (or may not) play role > in triggering the issue. > > http://appid.appspot.com redirects correctly to https://appid.appspot.com > http://customdomain -> returns 403 > https://customdomain -> works > > Thanks for a very good and beautifully designed service otherwise > Jan > -- 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/-/W1SAjNtfKpMJ. 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.
