Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Info

Proxy support is available for:

  • HTTP APL functions

  • HTTP Batch agent

  • GCP agentsPubSub Subscriber agent

  • GCP PubSub Publisher agent

  • GCP BigQuery agent

  • HTTP/2 Client agent

  • Salesforce Streaming agent

  • Web Services agents

...

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: Execution Context .

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

  • http.proxyHost

  • https.proxyHost

...

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

Some JDK versions support a system property that is used to disable certain proxy authentication schemes. This is controlled by two system properties:

  • jdk.http.auth.proxying.disabledSchemes – for HTTP traffic

  • jdk.http.auth.tunneling.disabledSchemes – for HTTPS traffic

These properties contain a list of authentication schemes that are disabled. In particular, in some JDK versions default jdk.http.auth.tunneling.disabledSchemes to “Basic" which has the effect of disabling basic authentication by default. To use basic authentication, you may need to setone or both of following system properties to ensure that they do not include “Basic". See the example configuration below.

...