Rules to Enable Next-hop Proxies for SOCKS Traffic
You can add various rules to the Next Hop Proxy rule set, using different criteria for setting up a next-hop proxy.
The following rule enables a next-hop proxy for a request that was received from a client of Web Gateway with an IP address that is on a particular list.
Name Enable next-hop proxy for SOCKS traffic if received from listed client Criteria Action Client.IP matches in list Client IPs –> Continue Enable Next Hop Proxy<SOCKS Next Hop Proxy>
The rule uses the Client.IP property to check whether the IP address of the client that a request was received from is on the list.
In this case, an event enables a next-hop proxy for this traffic. The event is executed with particular settings that you can configure to specify, for example, the version of the SOCKS protocol that should be used.
The next rule enables a next-hop proxy if the embedded protocol under the SOCKS protocol is HTTP.
Name
Enable next-hop proxy for SOCKS traffic with embedded HTTP protocol
Criteria Action
ProtocolDetector.DetectedProtocol<Default> equals "HTTP" –> Continue Enable Next Hop Proxy<Embedded
Protocol HTTP Next Hop Proxy>
The rule uses the ProtocolDetector.DetectedProtocol< property to check whether the embedded protocol is HTTP.
In this case, an event enables a next-hop proxy for this traffic. The event is executed with particular settings that you can configure to specify, for example, the version of the SOCKS protocol that should be used.
When using this rule, you also need to enable the option Determine next-hop proxy after receiving embedded data in the settings for the Protocol Detector module (or engine).
The next rule enables a next-hop proxy if the embedded protocol under the SOCKS protocol is HTTPS.
Name
Enable next-hop proxy for SOCKS traffic with embedded HTTPS protocol
Criteria Action
ProtocolDetector.DetectedProtocol<Default> equals "HTTPS" –> Continue Enable Next Hop Proxy<Embedded
Protocol HTTPS Next Hop Proxy>
The rule uses the ProtocolDetector.DetectedProtocol< property to check whether the embedded protocol is HTTP.
In this case, an event enables a next-hop proxy for this traffic. The event is executed with particular settings that you can configure to specify, for example, the version of the SOCKS protocol that should be used.
When using this rule, you also need to enable the option Determine next-hop proxy after receiving embedded data in the settings for the Protocol Detector module (or engine).
The next rule enables a next-hop proxy for any embedded protocol under the SOCKS protocol.
Name
Enable next-hop proxy for SOCKS traffic with any embedded protocol
Criteria Action
Connection.Protocol.Parent equals " SOCKS" –> Continue Enable Next Hop Proxy<Embedded Protocol Next
Hop Proxy>
The rule uses the Connection.Protocol.Parent property to check whether the SOCKS protocol appears as the parent protocol in a request for forwarding SOCKS traffic to the web. If SOCKS appears as the parent protocol, it means that there must be an embedded protocol.
In this case, an event enables a next-hop proxy for this traffic. The event is executed with particular settings that you can configure to specify, for example, the version of the SOCKS protocol that should be used.
The next rule is very similar to the preceding rule. It enables a next-hop proxy for traffic under the SOCKS protocol or traffic that goes on under the HTTP protocol directly, without being embedded in the SOCKS protocol.
Name Enable next-hop proxy for SOCKS traffic with any embedded protocol Criteria Action Connection.Protocol.Parent equals " SOCKS" OR –> Continue Enable Next Hop Proxy<Embedded Connection.Protocol equals "HTTP" Protocol Next Hop Proxy>