Class: Google::Cloud::Tasks::V2beta2::AppEngineHttpRequest

Inherits:
Object
  • Object
show all
Defined in:
lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb

Overview

App Engine HTTP request.

The message defines the HTTP request that is sent to an App Engine app when the task is dispatched.

This proto can only be used for tasks in a queue which has app_engine_http_target set.

Using AppEngineHttpRequest requires appengine.applications.get Google IAM permission for the project and the following scope:

https://www.googleapis.com/auth/cloud-platform

The task will be delivered to the App Engine app which belongs to the same project as the queue. For more information, see How Requests are Routed and how routing is affected by dispatch files. Traffic is encrypted during transport and never leaves Google datacenters. Because this traffic is carried over a communication mechanism internal to Google, you cannot explicitly set the protocol (for example, HTTP or HTTPS). The request to the handler, however, will appear to have used the HTTP protocol.

The AppEngineRouting used to construct the URL that the task is delivered to can be set at the queue-level or task-level:

The url that the task will be sent to is:

Tasks can be dispatched to secure app handlers, unsecure app handlers, and URIs restricted with login: admin. Because tasks are not run as any user, they cannot be dispatched to URIs restricted with login: required Task dispatches also do not follow redirects.

The task attempt has succeeded if the app's request handler returns an HTTP response code in the range [200 - 299]. The task attempt has failed if the app's handler returns a non-2xx response code or Cloud Tasks does not receive response before the deadline. Failed tasks will be retried according to the retry configuration. 503 (Service Unavailable) is considered an App Engine system error instead of an application error and will cause Cloud Tasks' traffic congestion control to temporarily throttle the queue's dispatches. Unlike other types of task targets, a 429 (Too Many Requests) response from an app handler does not cause traffic congestion control to throttle the queue.

Instance Attribute Summary collapse

Instance Attribute Details

#app_engine_routingGoogle::Cloud::Tasks::V2beta2::AppEngineRouting



222
# File 'lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb', line 222

class AppEngineHttpRequest; end

#headersHash{String => String}



222
# File 'lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb', line 222

class AppEngineHttpRequest; end

#http_methodGoogle::Cloud::Tasks::V2beta2::HttpMethod



222
# File 'lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb', line 222

class AppEngineHttpRequest; end

#payloadString



222
# File 'lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb', line 222

class AppEngineHttpRequest; end

#relative_urlString



222
# File 'lib/google/cloud/tasks/v2beta2/doc/google/cloud/tasks/v2beta2/target.rb', line 222

class AppEngineHttpRequest; end