A target HTTP proxy is a component of Google Cloud HTTP load balancers.
targetHttpProxies are used by global external Application Load Balancers, classic Application Load Balancers, cross-region internal Application Load Balancers, and Traffic Director.
regionTargetHttpProxies are used by regional internal Application Load Balancers and regional external Application Load Balancers.
[Output Only] The unique identifier for the resource. This identifier is defined by the server.
creationTimestamp
string
[Output Only] Creation timestamp in RFC3339 text format.
name
string
Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
description
string
An optional description of this resource. Provide this property when you create the resource.
selfLink
string
[Output Only] Server-defined URL for the resource.
urlMap
string
URL to the UrlMap resource that defines the mapping from URL to the BackendService.
region
string
[Output Only] URL of the region where the regional Target HTTP Proxy resides. This field is not applicable to global Target HTTP Proxies.
proxyBind
boolean
This field only applies when the forwarding rule that references this target proxy has a loadBalancingScheme set to INTERNAL_SELF_MANAGED.
When this field is set to true, Envoy proxies set up inbound traffic interception and bind to the IP address and port specified in the forwarding rule. This is generally useful when using Traffic Director to configure Envoy as a gateway or middle proxy (in other words, not a sidecar proxy). The Envoy proxy listens for inbound requests and handles requests when it receives them.
The default is false.
httpFilters[]
string
URLs to networkservices.HttpFilter resources enabled for xDS clients using this configuration. For example, https://networkservices.googleapis.com/v1alpha1/projects/project/locations/locationhttpFilters/httpFilter Only filters that handle outbound connection and stream events may be specified. These filters work in conjunction with a default set of HTTP filters that may already be configured by Traffic Director. Traffic Director will determine the final location of these filters within xDS configuration based on the name of the HTTP filter. If Traffic Director positions multiple filters at the same location, those filters will be in the same order as specified in this list.
httpFilters only applies for loadbalancers with loadBalancingScheme set to INTERNAL_SELF_MANAGED. See ForwardingRule for more details.
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking. This field will be ignored when inserting a TargetHttpProxy. An up-to-date fingerprint must be provided in order to patch/update the TargetHttpProxy; otherwise, the request will fail with error 412 conditionNotMet. To see the latest fingerprint, make a get() request to retrieve the TargetHttpProxy.
A base64-encoded string.
httpKeepAliveTimeoutSec
integer
Specifies how long to keep a connection open, after completing a response, while there is no matching traffic (in seconds). If an HTTP keep-alive is not specified, a default value (610 seconds) will be used.
For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds.
For classic Application Load Balancers, this option is not supported.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-28 UTC."],[[["\u003cp\u003eTarget HTTP Proxies are a critical component of Google Cloud HTTP load balancers, used by both global and regional load balancers, as well as Traffic Director.\u003c/p\u003e\n"],["\u003cp\u003eThere are two types of Target HTTP Proxies within Google Compute Engine: global, used by global external and classic Application Load Balancers, and regional, used by regional external and internal Application Load Balancers.\u003c/p\u003e\n"],["\u003cp\u003eForwarding rules connect to a Target HTTP Proxy, which in turn directs traffic according to the rules defined in a URL map.\u003c/p\u003e\n"],["\u003cp\u003eThe JSON representation of a Target HTTP Proxy includes fields like \u003ccode\u003ekind\u003c/code\u003e, \u003ccode\u003eid\u003c/code\u003e, \u003ccode\u003ename\u003c/code\u003e, \u003ccode\u003eurlMap\u003c/code\u003e, and \u003ccode\u003ehttpFilters\u003c/code\u003e, among others, that define its properties and behavior.\u003c/p\u003e\n"],["\u003cp\u003eTargetHttpProxy resources can be managed using methods like \u003ccode\u003eget\u003c/code\u003e, \u003ccode\u003einsert\u003c/code\u003e, \u003ccode\u003edelete\u003c/code\u003e, \u003ccode\u003epatch\u003c/code\u003e, and \u003ccode\u003esetUrlMap\u003c/code\u003e, which control their lifecycle and configuration within a project.\u003c/p\u003e\n"]]],[],null,["# REST Resource: targetHttpProxies\n\n- [Resource: TargetHttpProxy](#TargetHttpProxy)\n - [JSON representation](#TargetHttpProxy.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: TargetHttpProxy\n-------------------------\n\nRepresents a Target HTTP Proxy resource.\n\nGoogle Compute Engine has two Target HTTP Proxy resources:\n\n- [Global](/compute/docs/reference/rest/beta/targetHttpProxies)\n- [Regional](/compute/docs/reference/rest/beta/regionTargetHttpProxies)\n\nA target HTTP proxy is a component of Google Cloud HTTP load balancers.\n\n- targetHttpProxies are used by global external Application Load Balancers, classic Application Load Balancers, cross-region internal Application Load Balancers, and Traffic Director.\n- regionTargetHttpProxies are used by regional internal Application Load Balancers and regional external Application Load Balancers.\n\nForwarding rules reference a target HTTP proxy, and the target proxy then references a URL map. For more information, read [Using Target Proxies](/load-balancing/docs/target-proxies) and [Forwarding rule concepts](/load-balancing/docs/forwarding-rule-concepts)."]]