Configuring Proxies

Use a proxy to connect to nodes for transfer initiation and node browsing.

Go to Configuration > Proxy to configure global HTTP and FASP proxies.

HTTP Proxy Vs. Fasp Proxy

Console supports using two types of proxies: HTTP and FASP proxies.

The FASP proxy is only used when browsing a node through an SSH endpoint. Console uses the HTTP proxy for all other scenarios:
  • Browsing a source or destination node using a Node API endpoint
  • Retrieving a transfer token from the destination node when starting a token-based transfer
  • Starting a transfer at the source node
The following diagrams show different scenarios in which Console goes through a proxy to communicate with a node:

Note: When the FASP proxy between the source node and destination node is different from the global FASP proxy used by Console. The proxy between the nodes is defined during creation of a simple or smart transfer (More Options > Connection).

Configuring Proxies

Go to Configuration > Proxy to configure global HTTP and FASP proxies. You can enable one or both proxies. Both HTTP and FASP proxies take similar parameters:

Field Description
Address Proxy IP address or domain name
Port Proxy port number
SSL (FASP proxy only) Enable or disable use of SSL
Username Proxy username
Password Proxy user password

Creating Proxy Exclusion Rules

You can exclude a range of IP addresses and domain names from going through proxies by creating proxy exclusion rules. Define a rule by selecting the rule type and providing a range of addresses.

For example, you can exclude all IP Addresses starting with 192 and all domain names ending in ibm.com with the following two rules:

Order Rule Type Address
1 Exclude 192.*
2 Exclude *.ibm.com
Console applies the first matched rule. The order of your rules is important, especially if you are including some addresses and excluding others. For example, to include 10.0.71.51, but exclude all other 10.X addresses:
Order Rule Type Address
1 Include 10.0.71.51
2 Exclude 10.*
Console uses configured proxies to connect to a node at 10.0.71.51, even though all 10.X addresses are excluded, because the address matched the inclusion rule first. In the reverse case, however, Console does not use configured proxies for 10.0.71.51, even though the address is included, the address matched the exclusion rule first:
Order Rule Type Address
1 Exclude 10.*
2 Include 10.0.71.51

If an address doesn't match any of the rules, Console applies the global proxy as usual.