App Engine target. The job will be pushed to a job handler by means of an HTTP request via an [http_method][google.cloud.scheduler.v1.AppEngineHttpTarget.http_method] such as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an HTTP response code in the range [200 - 299]. Error 503 is considered an App Engine system error instead of an application error. Requests returning error 503 will be retried regardless of retry configuration and not counted against retry counts. Any other response code, or a failure to receive a response before the deadline, constitutes a failed attempt.
App Engine Routing setting for the job.
HTTP request headers. This map contains the header field
names and values. Headers can be set when the job is created.
Cloud Scheduler sets some headers to default values: -
User-Agent: By default, this header is "AppEngine-
Google; (+http://code.google.com/appengine)". This header
can be modified, but Cloud Scheduler will append
"AppEngine-Google; (+http://code.google.com/appengine)" to
the modified User-Agent. - X-CloudScheduler: This
header will be set to true. If the job has an
body,
Cloud Scheduler sets the following headers: - Content-
Type: By default, the Content-Type header is set to
"application/octet-stream". The default can be overridden
by explictly setting Content-Type to a particular media
type when the job is created. For example, Content-Type
can be set to "application/json". - Content-
Length: This is computed by Cloud Scheduler. This value
is output only. It cannot be changed. The headers below are
output only. They cannot be set or overridden: -
X-Google-*: For Google internal use only. -
X-AppEngine-*: For Google internal use only. In addition,
some App Engine headers, which contain job-specific
information, are also be sent to the job handler.
Classes
HeadersEntry
API documentation for scheduler_v1.types.AppEngineHttpTarget.HeadersEntry class.