HTTP proxy support

  • Updated

The New LucidLink Client supports the following HTTP proxy options. In conjunction, calls to endpoints from the LucidLink client application now use FQDN, which allows either FQDN or IP whitelisting on your proxy server.

Automatically detected

  1. OS proxy configuration
  2. PAC (Proxy Auto-Configuration) file and WPAD

When the proxy is configured using the methods above, you can use either an IP address or a hostname.

Manually specified

  1. The lucid command override with the --proxy option from the CLI:
--proxy arg              Specify a proxy server to tunnel all communication. Use the following format: [protocol://][user:password@]proxyhost[:port]. Supported protocols: http. Not applicable for Azure object storage.

Note: Currently, only an IP address is supported when specifying the --proxy argument via CLI. Proxy by Hostname is only supported with proxy auto-detection.

Was this article helpful?

0 out of 0 found this helpful