Many organizations use a Web Proxy to secure outbound internet access. A Web Proxy acts as an intermediary between internal (intranet) HTTP clients and the internet.
A Web Proxy may be used to:
- Provide a single network egress point for internal systems.
- Cache frequently accessed web pages to improve performance.
- Provide access control, content filtering, and logging on internet traffic.
If your organization uses a Web Proxy, LightWave Client can be configured to use it just like any other HTTP client in your organization. This allows the NonStop to use the same network egress path as other HTTP clients, and eliminates the need to configure special outbound firewall rules for the NonStop. The only requirement is that the Web Proxy uses the standard HTTP proxy protocol and is network accessible from the NonStop system.
The CLIENT process is configured to use a proxy using the --http-proxy-host and optionally, the -http-proxy-credentials command line options. The -http-proxy-host option specifies the host name and port of the Web Proxy device. If the Web Proxy requires authentication, the -http-proxy-credentials option is used to provide the authentication credentials. The following sample Pathway configuration illustrates how to configure the CLIENT process with a proxy:
SERVER MY-SERVICE CPUS (0:1) CREATEDELAY 0 SECS ( ... other serverclass options ... ) PARAM API "SVCAPI" PARAM BASE-URL "https://service.example.com/api/v1" PARAM LOG "LWCLOG INFO" PARAM HTTP-PROXY-HOST "https://squid.internal.example.com:3128" PARAM HTTP-PROXY-CREDENTIALS "nonstop:secret" PARAM TCPIP-PROCESS "$ztc0" PROGRAM \NODE.$SYSTEM.LWC.CLIENT
More information on CLIENT process configuration options can be found in the LightWave Client Command Line Reference.