[google-appengine] Re: How to enable Managed SSL on App Engine when using CloudFlare CDN

Managed security will need to check existence of canonical name (CNAME) record with the value of *ghs.googlehosted.com* for your domain/subdomain. If you're serving *www.example.com* on CloudFlare, you may map *w3.example.com* as custom sub-domain on GAE and enable managed security for it.

[google-appengine] Re: Google App Engine - Region

We need this too for GAE Standard Environment... basically a GAE Std in EU going to backend databases hosted on VMs in EU, and GAE Std in US going to backend databases hosted on VMs in US. We need both in the same project to share services accounts, datastore tables, storeage buckets, etc. On

[google-appengine] Re: Google App Engine multiple regions

We need this too for GAE Standard Environment... basically an GAE in EU going to backend databases hosted on VMs in EU, and GAE in US going to backend databases hosted on VMs in US. On Monday, June 20, 2016 at 5:13:12 AM UTC-4, Yon Dev wrote: > > I am evaluating whether GAE would be a good fit

[google-appengine] Re: GAE std deployed to multiple regions within the same project?

This is currently not possible. However, our engineering team is working on a solution to cross-region load balance App Engine Flexible and Standard. There is no ETA for the release but you can follow the Public Feature Request for updates. It seems

[google-appengine] Re: Datastore on flex nodejs appengine isn't working

Hi Tony I have the same issue, did you find a way to solve it? On Wednesday, February 1, 2017 at 4:16:00 PM UTC+2, Tony Stark wrote: > > Since yesterday does not work datastore through the flex evironment. > Application just not receives the response from the datastore. If I run the >

Re: [google-appengine] Re: gcloud vs. goapp for GO appengine

My main concern is, what is going to happen to goapp test? This is a critical part of our toolchain that tests our code under appengine go (as opposed to non-appengine go, which I installed via brew). I am not seeing a documented replacement for this tool anywhere. As a temporary hack to keep

[google-appengine] Re: GAE PubSub PUSH results in 400, endpoint is OK otherwise

400 Bad Request means that your App Engine endpoint does not know how to handle the POST request from Pub/Sub. You need to configure your App Engine endpoint to accept POST requests to properly handle your pushed Pub/Sub messages. Note that Google Groups is meant for general product

[google-appengine] GAE std deployed to multiple regions within the same project?

Is there any chance I will be able to have GAE std deployed to multiple regions within the same project? We want a GAE std in US accessing databases in the US, with a European GAE std accessing databases in the EU. We want them on the same project so all of the security keys, and especially

[google-appengine] GAE PubSub PUSH results in 400, endpoint is OK otherwise

I am starting with a push PubSub, and manually test a PUSH PubSub service. To the end I created a topic, a push subscription, and then manually submit a message from the google web console to a GAE app with a https endpoint. These manual messages result in 400 (see below) in the logs. curl

[google-appengine] Re: How to enable Managed SSL on App Engine when using CloudFlare CDN

While that works it's not completely secure, only Full SSL (strict) or Full SSL (origin ca)* is, not plain Full SSL. In Full SSL mode Cloudflare doesn't verify the common name on the certificate served by AppEngine which is why it works as you described. If I enable Full SSL (strict) using the

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

If properly responding to the health check with a message body *res.status(200).send('');* as the documentation states causes the health checks to fail, that would indeed warrant an issue to be reported in the PIT (public issue tracker). Note that responding to health checks is not required

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hi Jordan, we would like to share with you what we have found. We have delete our custom health check that was an handler responding with 200 OK as follows: app.get('/_ah/health', function (req, res) { res.sendStatus(200); }); It looks like this has solved the problem as we *do not* see any