Forward proxies provide a single point through which multiple machines send requests to an external server. They can enforce security policies, log and analyze requests, and perform other actions so that requests adhere to your business rules.
Using a forward proxy in Apigee hybrid,
you can intercept and manage all egress traffic from your Kubernetes cluster. This includes API
proxy requests to Target Endpoints and communication with *.googleapis.com that the hybrid
runtime makes for its debug and analytics pipeline and for policies like MessageLogging.
To use an HTTP forward proxy between hybrid and the TargetEndpoint, you must configure
the outbound proxy settings in your overrides file. These environment-scoped properties
route target requests from hybrid to the HTTP forward proxy. You also need to ensure
use.proxy is set to "true" for any TargetEndpoint that you want to go through an HTTP
forward proxy. See the bottom of the page for instructions.
To configure a hybrid environment for forwarding proxying, add
the envs.httpProxy property to your overrides file and apply it to the
cluster. For example:
envs:
- name: test
httpProxy:
scheme: HTTP
host: 10.12.0.47
port: 3128
...For details on each of the envs.httpProxy configuration properties refer to the
Configuration property reference.
Forward proxying is configured for an environment; all traffic going from API proxies in that environment to backend targets goes through the specified HTTP forward proxy. If the traffic for a specific target of an API proxy should go directly to the backend target, bypassing the forward proxy, then set the following property in the TargetEndpoint to override the HTTP forward proxy:
<Property name="use.proxy">false</Property>
For more information on setting the TargetEndpoint properties, including how to configure the connection to the target endpoint, see Endpoint properties reference.
Set use.proxy to "true" for any TargetEndpoint that you want to go through
an HTTP forward proxy:
<Property name="use.proxy">true</Property>