google-app-engine

问题 I want to map notification.api.example.co.uk to a specific app engine service called notification-api I've added a custom domain on app engine called api.example.com successfully, so was hoping the following dispatch.yaml would be sufficient: dispatch: - url: "notification.api.example.co.uk/*" service: notification-api I was hoping, therefore, any request, for example, a POST to notification.api.example.co.uk/test-api would route the request to service and render a response, but it doesn't

问题 I have two services running on Google App Engine (flex, same project), and I'd like one service to call the other using HTTPS. On top of this, I've setup the firewall, only allowing 0.1.0.40 and 10.0.0.1 . I'm also setting the X-Appengine-Inbound-Appid header in the request. Unfortunately, I'm getting a "403 Access is forbidden" error (which disappears when disabling the firewall). Right now, I am using the xxx.appspot.com URL to call the service. Should I use some internal URL instead? It

问题 I would like to know if there is any way to remove the server name(Google Frontend) from the google app engine response header to hide that the app is deployed on GAE. 回答1: Nope. DNS also gives you away. 回答2: Consider a reverse proxy in front of your GAE app. The DNS will be to your reverse proxy server. You can mess with the response headers on the way back out. This starts to break down the killer advantage of GAE - that it "easily scales on googles infrastructure" - but a single nginx

问题 I would like to know if there is any way to remove the server name(Google Frontend) from the google app engine response header to hide that the app is deployed on GAE. 回答1: Nope. DNS also gives you away. 回答2: Consider a reverse proxy in front of your GAE app. The DNS will be to your reverse proxy server. You can mess with the response headers on the way back out. This starts to break down the killer advantage of GAE - that it "easily scales on googles infrastructure" - but a single nginx

问题 We are using Google Cloud instances (AppEngine) to synchronize data for our users with their Google Calendars (through the Calendar API). Basically, we provide a task management solution and the tasks should be synchronized (unidirectional) with the calendars they (the users) provide us access for. How it all works: 1. We ask the users to grant access to their Google Account. 2. We ask them to select the desired calendar or offer the possibility of creating a new one under their account. 3.

问题 We are using Google Cloud instances (AppEngine) to synchronize data for our users with their Google Calendars (through the Calendar API). Basically, we provide a task management solution and the tasks should be synchronized (unidirectional) with the calendars they (the users) provide us access for. How it all works: 1. We ask the users to grant access to their Google Account. 2. We ask them to select the desired calendar or offer the possibility of creating a new one under their account. 3.

问题 We are using Google Cloud instances (AppEngine) to synchronize data for our users with their Google Calendars (through the Calendar API). Basically, we provide a task management solution and the tasks should be synchronized (unidirectional) with the calendars they (the users) provide us access for. How it all works: 1. We ask the users to grant access to their Google Account. 2. We ask them to select the desired calendar or offer the possibility of creating a new one under their account. 3.

问题 I am following this tutorial on Google Cloud Platform and am finding that the SIMPLE app launches successfully up on port 8080 but when I head over to the browser to view it externally, I get an internal server error. The tutorial can be found here: https://cloud.google.com/appengine/docs/standard/nodejs/building-app/deploying-web-service I am using Win8.1 using the GCP cloud shell terminal. I have also tried updating my npm packages, moving my yaml, nodejs files to the next higher directory

问题 I am following this tutorial on Google Cloud Platform and am finding that the SIMPLE app launches successfully up on port 8080 but when I head over to the browser to view it externally, I get an internal server error. The tutorial can be found here: https://cloud.google.com/appengine/docs/standard/nodejs/building-app/deploying-web-service I am using Win8.1 using the GCP cloud shell terminal. I have also tried updating my npm packages, moving my yaml, nodejs files to the next higher directory

问题 I've just deployed my app in the app engine (www.mibar.es) and when it is not in use for a long while, it takes more than 40 seconds for it to wake up and serve the first request. After that one, it takes a second to serve the next requests. How can I reduce that time? Why is not always ready? How can I make it to be always ready? I doesn't show any error on the GCP console and searching for this same problem I've found out about https://cloud.google.com/appengine/docs/standard/java11