socks.config

Configuration Files > socks.config

socks.config

Help | Content Gateway | Version 7.7.3

The socks.config file specifies:

SOCKS servers that the proxy must use to access specific origin servers, and the order in which the proxy goes through the SOCKS server list.

Origin servers that Content Gateway accesses directly, without going through a SOCKS server.


	Note It is recommended that all SOCKS configuration be performed in the Content Gateway Manager.


	Important After you modify this file, you must restart the proxy.

Traffic that does not match a manually configured rule is handled via a default rule. A default rule is constructed for each SOCKS server with the default option enabled in the Socks Servers table. Default rules are created automatically and displayed on the SOCKS Server page. Default rules are not written in the socks.config file. The destination IP address is 'All'.

Format

To specify SOCKS servers that the proxy must use to reach specific origin servers, add rules to the socks.config file in the following format:

dest_ip=ipaddress socksparent="alias1" [round_robin=value]

where:

ipaddress is the origin server IP address or range of IP addresses separated by - or /.

alias1 is the alias name of the SOCKS server named in the SOCKS Servers list.

value is either strict if you want Content Gateway to try the SOCKS servers one by one, or false if you do not want round-robin selection to occur.

To specify origin servers that you want Content Gateway to access directly, without going through the SOCKS server(s), enter a rule in socks.config in the following format:

no_socks ipaddress

where ipaddress is a comma-separated list of the IP addresses or IP address ranges associated with the origin servers that you want Content Gateway to access directly. Do not specify the all networks broadcast address: 255.255.255.255.