Http target. The job will be pushed to the job handler by means of
an HTTP request via an
as HTTP POST, HTTP GET, etc. The job is acknowledged by means of an
HTTP response code in the range [200 - 299]. A failure to receive a
response constitutes a failed execution. For a redirected request,
the response returned by the redirected request is considered.
This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
Required. The full URI path that the request will be sent
to. This string must begin with either "http://" or
"https://". Some examples of valid values for
http://acme.com and https://acme.com/sales:8080.
Cloud Scheduler will encode some characters for safety and
compatibility. The maximum allowed URL length is 2083
characters after encoding.
The user can specify HTTP request headers to send with the
job's HTTP request. This map contains the header field names
and values. Repeated headers are not supported, but a header
value can contain commas. These headers represent a subset
of the headers that will accompany the job's HTTP request.
Some HTTP request headers will be ignored or replaced. A
partial list of headers that will be ignored or replaced is
- Host: This will be computed by Cloud Scheduler and
- Content-Length: This will be computed by Cloud
- User-Agent: This will be set to
- X-Google-*: Google internal use only.
- X-AppEngine-*: Google internal use only.
- X-CloudScheduler: This header will be set to true.
- X-CloudScheduler-JobName: This header will contain
the job name.
- X-CloudScheduler-ScheduleTime: For Cloud Scheduler
jobs specified in the unix-cron format, this header will
contain the job schedule time in RFC3339 UTC "Zulu"
The total size of headers must be less than 80KB.
HTTP request body. A request body is allowed only if the
HTTP method is POST, PUT, or PATCH. It is an error to set
body on a job with an incompatible
If specified, an
token will be generated and attached as an Authorization
header in the HTTP request.
This type of authorization can be used for many scenarios,
including calling Cloud Run, or endpoints where you intend
to validate the token yourself.
This field is a member of oneof_ authorization_header.