This page describes how App Engine applications issue HTTP and HTTPS requests and receive responses. To see code samples demonstrating how to issue HTTP and HTTPS requests from your App Engine application, see Issuing HTTP(S) Requests.
RequestsIn the App Engine Java 8 runtime, you can use the
java.net.URLConnectionabstract class, and related classes from the Java standard library, to make HTTP and HTTPS connections from your Java application.
Alternatively, you can also use the App Engine
URL Fetch API, which provides an implementation of the methods defined in
URLConnection by using the URL Fetch API. For information on using the native
Java classes versus the URL Fetch API, see
Advantages to using standard Java calls and not URL Fetch in Java 8.
An application can fetch a URL using either HTTP or HTTPS. The protocol that should be used is inferred by looking at the protocol in the target URL.
The URL to be fetched can use any port number in the following ranges:
If the port is not mentioned in the URL, the port is implied by the
protocol. HTTP requests occur on port
80, and HTTPS requests occur
Request methodsIf you issue requests through the standard Java
java.net.URLConnectionclass, you can use any supported HTTP method.
If you issue requests through the URL Fetch service, you can use any of the following HTTP methods:
A request can include HTTP headers and, for
requests, a payload.
Note that the URL Fetch service uses an HTTP/1.1 compliant proxy to fetch the result.
To prevent an application from causing an endless recursion of requests, a request handler is not allowed to fetch its own URL. It is still possible to cause an endless recursion with other means, so exercise caution if your application can be made to fetch requests for URLs supplied by the user.
Your application can set HTTP headers for the outgoing request.
When sending an HTTP
POST request, if a
Content-Type header is
not set explicitly, the header is set to
This is the content type used by web forms.
For security reasons, the following headers cannot be modified by the application:
These headers are set to accurate values by App Engine as
appropriate. For example, App Engine calculates the
Content-Length header from the request data and adds it to
the request prior to sending.
The following headers indicate the application ID of the requesting app:
User-Agent. This header can be modified, but App Engine will append an identifier string to allow servers to identify App Engine requests. The appended string has the format
"AppEngine-Google; (+http://code.google.com/appengine; appid: APPID)", where
APPIDis your app's identifier.
X-Appengine-Inbound-Appid. This header cannot be modified, and is added automatically if the request is sent via the URL Fetch service when the follow redirects parameter is set to
You can set a deadline, or timeout, for a request. By default, the
timeout for a request is 5 seconds.
The maximum deadline is 60 seconds for HTTP(S) requests and 60 seconds
for Task Queue and cron job requests.
When using the
URLConnection abstract class with URL Fetch, the service uses the
connection timeout (
setConnectTimeout()) plus the read timeout
setReadTimeout()) as the deadline.
You can send synchronous requests and asynchronous requests. The following behavior applies to the URL Fetch API:
- Synchronous requests: The fetch call waits until the remote host returns a result, and then returns control to the application. If the maximum wait time for the fetch call is exceeded, the call raises an exception.
- Asynchronous requests: The URL Fetch service starts the request, then returns immediately with an object. The application can perform other tasks while the URL is being fetched. When the application needs the results, it calls a method on the object, which waits for the request to finish if necessary, then returns the result. If any URL Fetch requests are pending when the request handler exits, the application server waits for all remaining requests to either return or reach their deadline before returning a response to the user.
Secure connections and HTTPS
Your application can fetch a URL securely by using HTTPS to connect to secure servers. Request and response data are transmitted over the network in encrypted form.
If you use the URL Fetch API, note that the URL Fetch proxy does not validate
the host it is contacting. The proxy server cannot detect man-in-the-middle
attacks between App Engine and the remote host when using HTTPS.
You can use the
class in the
URLFetchService API to enable host validation.
If you use the URL Fetch API, note that the URL Fetch service returns all response data, including the response, code, headers, and body.
By default, if the URL Fetch service receives a response with a redirect code, the service will follow the redirect. The service will follow up to five redirect responses, then return the final resource. You can instruct the URL Fetch service to not follow redirects and instead return a redirect response to the application.
Using URL Fetch on the development server
When your application is running on the App Engine development server on your computer, calls to the URL Fetch service are handled locally. The development server fetches URLs by contacting remote hosts directly from your computer, using whatever network configuration your computer is using to access the Internet.
When testing the features of your application that fetch URLs, make sure that your computer can access the remote hosts.
Quotas and limits for URL FetchFor the Java 8 runtime, you can use the standard Java
java.net.URLConnectionAPI, instead of URLFetch, where these quota and limit considerations do not apply.
For information about URL Fetch service quotas, see Quotas. To see the current quota usage of your application, go to the Quota Details page in the Google Cloud Console.
In addition, the following limits apply to the use of the URL Fetch service:
|Request size||10 megabytes|
|Request header size||16 KB (Note that this limits the maximum length of the URL that can be specified in the header)|
|Response size||32 megabytes|
|Maximum deadline (request handler)||60 seconds|
|Maximum deadline (Task Queue and cron job handler)||60 seconds|
Run code samples and get guidance on how to issue requests from your application in Issuing HTTP(S) Requests.