Note 

Specifies the version of SOCKS used on your SOCKS server. Content Gateway supports SOCKS version 4 and version 5.

Note: Content Gateway does not perform user authentication with the client. However, the proxy can perform user name and password authentication with a SOCKS server running SOCKS version 5.

Click Apply before you click Close; otherwise, all configuration changes are lost.
Displays a table listing the rules in the socks.config file that specify the SOCKS servers that Content Gateway must go through to access specific origin servers, and the order in which Content Gateway goes through the SOCKS server list.
Lists the socks.config file rules. Select a rule to edit it. The buttons on the left of the box allow you to delete or move the selected rule up or down in the list.
Select Route through SOCKS server to specify the origin servers that you want the proxy to route through a SOCKS server.
Select Do not route through SOCKS server to specify the origin servers that you want the proxy to access directly, bypassing the SOCKS server(s).
For Route through SOCKS server, specify either a single IP address or a range of IP addresses of origin servers for which Content Gateway must use the SOCKS servers specified in the SOCKS Servers field below.
For Do not route through SOCKS server, specify the IP addresses of the origin servers that you want the proxy to access directly (without going through the SOCKS server). You can enter a single IP address, a range of IP addresses, or a list of IP addresses. Separate each entry in the list with a comma. Do not specify the all networks broadcast address: 255.255.255.255.
For a Route through SOCKS server rule, select the SOCKS server(s) through which to route requests.
Click Apply before you click Close; otherwise, all configuration changes will be lost.