Region ID
The REGION_ID is an abbreviated code that Google assigns
based on the region you select when you create your app. The code does not
correspond to a country or province, even though some region IDs may appear
similar to commonly used country and province codes. For apps created after
February 2020, REGION_ID.r is included in
App Engine URLs. For existing apps created before this date, the
region ID is optional in the URL.
Learn more about region IDs.
Use this reference page for details about what HTTP headers are supported . To understand how App Engine receives requests and sends responses, see How Requests Are Handled.
Request headers
An incoming HTTP request includes the HTTP headers sent by the client. For security purposes, some headers are sanitized, amended, or removed by intermediate proxies before they reach the application.
Headers removed from incoming requests
The following headers are removed from incoming requests if a client sends them:
Headers with names that match the
X-Google-*pattern. This name pattern is reserved for Google.Headers with names that match App Engine-specific headers. Only exact, case-insensitive matches are removed. For example, headers named
X-Appengine-CountryorX-AppEngine-Countrywill be removed butX-Appengine-Cntrywill not.
App Engine-specific headers
As a service to the app, App Engine adds the following headers to all requests:
X-Appengine-Country- Country from which the request originated, as an ISO 3166-1
alpha-2 country code.
App Engine determines this code from the client's IP address. Note that
the country information is not derived from the WHOIS database; it's possible
that an IP address with country information in the WHOIS database will not have
country information in the
X-Appengine-Countryheader. Your application should handle the special country codeZZ(unknown country). X-Appengine-Region- Name of region from which the request originated. This value only makes
sense in the context of the country in
X -Appengine-Country. For example, if the country is "US" and the region is "ca", that "ca" means "California", not Canada. The complete list of valid region values is found in the ISO-3166-2 standard. X-Appengine-City- Name of the city from which the request originated. For example, a request
from the city of Mountain View might have the header value
mountain view. There is no canonical list of valid values for this header. If the city can't be resolved, the header value is set to?. X-Appengine-CityLatLong- Latitude and longitude of the city from which the request originated. This
string might look like "37.386051,-122.083851" for a request from Mountain View.
If the city can't be resolved, the header value is set to
0.000000,0.000000. X-Cloud-Trace-Context- A unique identifier for the request used for Cloud Trace and Cloud Logging. There isn't an option to disable this header or choose the sampling rate for tracing since all App Engine standard environment apps are traced automatically.
X-Forwarded-For: [CLIENT_IP(s)], [global forwarding rule IP]A comma-delimited list of IP addresses through which the client request has been routed. The first IP in this list is generally the IP of the client that created the request. The subsequent IPs provide information about proxy servers that also handled the request before it reached the application server. For example:
X-Forwarded-For: clientIp, proxy1Ip, proxy2IpX-Forwarded-Proto [http | https]Shows
httporhttpsbased on the protocol the client used to connect to your application.The Google Cloud Load Balancer terminates all
httpsconnections, and then forwards traffic to App Engine instances overhttp. For example, if a user requests access to your site viahttps://PROJECT_ID.REGION_ID.r.appspot.com, the X- Forwarded-Proto header value ishttps.
In addition, App Engine may set the following headers which are for internal use by App Engine:
X-Appengine-HttpsX-Appengine-User-IPX-Appengine-Api-TicketX-Appengine-Request-Log-IdX-Appengine-Default-Version-HostnameX-Appengine-Timeout-Ms