Please note that the contents of this offline web site may be out of date. To access the most recent documentation visit the online version .
Note that links that point to online resources are green in color and will open in a new window.
We would love it if you could give us feedback about this material by filling this form (You have to be online to fill it)



Target HTTP Proxies

Limited Preview

This is a Limited Preview release of HTTP load balancing. As a result, it might be changed in backward-incompatible ways and is not recommended for production use. It is not subject to any SLA or deprecation policy. Request to be whitelisted to use this feature .


Target HTTP proxies are referenced by one or more global forwarding rules and route the incoming HTTP requests to a URL map. You manage target HTTP proxies by using either the gcloud compute command-line tool or the REST API methods.

Target HTTP proxy properties

See the TargetHttpProxies resource for descriptions of the properties that available when working with target HTTP proxies through either the REST API or the gcloud compute command-line tool.

Adding a target HTTP proxy

To add a target HTTP proxy with gcloud compute , use the target-http-proxies create command:

$ gcloud compute target-http-proxies create HTTP_PROXY \
    --url-map URL_MAP [--description DESCRIPTION]

To create a target HTTP proxy through the API, send a POST request to:

POST https://www.googleapis.com/v1/compute/projects/<project-id>/global/targetHttpProxies

{
  "name": NAME,
  "urlMap": URL_MAP
}

Listing target HTTP proxies

To list target HTTP proxies with gcloud compute , use the target-http-proxies list command:

$ gcloud compute target-http-proxies list

In the API, send an empty GET request to the following URI:

https://www.googleapis.com/compute/v1/projects/<project-id>/global/targetHttpProxies

Getting a target HTTP proxy

To get information about a single target HTTP proxy with gcloud compute , use the target-http-proxies list command:

$ gcloud compute target-http-proxies get HTTP_PROXY

In the API, send an empty GET request to the following URI:

https://www.googleapis.com/compute/v1/projects/<project-id>/global/targetHttpProxies/<http-proxy>

Deleting a target HTTP proxy

To delete a target HTTP proxy, you must first delete any global forwarding rules that reference it.

To delete a target HTTP proxy using gcloud compute , use the target-http-proxies delete command:

$ gcloud compute target-http-proxies delete HTTP_PROXY

In the API, send an empty DELETE request to the following URI:

https://www.googleapis.com/compute/v1/projects/<project-id>/global/targetHttpProxies/<http-proxy>

Updating a URL map for the target HTTP proxy

To update the URL map associated with a target HTTP proxy using gcloud compute , use the target-http-proxies update command:

$ gcloud compute target-http-proxies update HTTP_PROXY \
       --url-map URL_MAP

In the API, send a POST request to the following URI, passing the fully-qualified URI to the URL maps to add or remove in the request body:

POST https://www.googleapis.com/compute/v1/projects/<project-id>/global/targetHttpProxies/<http-proxy>/setUrlMap

{
 "urlMap": URL_MAP
}

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.