HTTP Proxy Support

MediationZone can be configured to route outgoing HTTP traffic through an HTTP proxy. This is commonly required in networking environments where the execution context has limited access to the internet. Proxy configuration has to be performed on each Execution Context (EC) that is required to route HTTP traffic through a proxy.

Proxy support is available for:

  • HTTP APL functions

  • HTTP Batch agent

  • GCP PubSub Subscriber agent

  • GCP PubSub Publisher agent

  • GCP BigQuery agent

  • HTTP/2 Client agent

  • Salesforce Streaming agent

This chapter has the following sections:

Configuring Proxy Support

Standard Java system properties are used to configure MediationZone to route HTTP traffic through an HTTP proxy. These properties must be configured at the Execution Context (EC) level for all execution contexts. Refer to proxy properties here:

At least one of these properties has to be set to use HTTP Proxy:

  • http.proxyHost

  • https.proxyHost

It is often necessary to provide a list of destinations that should not be routed through the proxy. This list can be configured using the proxy property http.nonProxyHosts. Note that this property, despite the name, applies to both http and https traffic.

Currently, only HTTP/1.1 has been verified to route through an HTTP proxy.

Authenticating the Proxy

MediationZone supports basic authentication to HTTP proxy. The username and password are configured using system properties. Refer to the proxy properties here:

Example Configuration

Here is an example of how to configure the system properties to use an HTTP Proxy.

Use the following command to edit the system properties.

mzsh topo open ec1

config {     classpath {}     jvmargs {         args=[]         maxMetaspace=[             "-XX:MaxMetaspaceSize=196M"         ]     }     properties {         mz.webserver.xframeoptions=DENY         pico.groups=""         ec.backlog.dir="/Users/mzadmin/mz9/mz9HttpProxy/tmp"         ec.webserver.port=9090         http.proxyHost=         http.proxyPort=3128         https.proxyHost=         https.proxyPort=3128         http.proxyUser=test         http.proxyPassword=DR-4-D999C75BC7A3C4AF1B4DAA7F134EEED9         https.proxyUser=test         https.proxyPassword=DR-4-D999C75BC7A3C4AF1B4DAA7F134EEED9         http.nonProxyHosts="localhost|*"         jdk.http.auth.proxying.disabledSchemes=""         jdk.http.auth.tunneling.disabledSchemes=""     }     vendor-jvmargs {         hp {}         sun {}     } }