Next Hop Proxy — Feature Configuration

After web requests received from your endpoints are filtered, they can be forwarded to the next-hop proxy servers that you have configured.

You can improve performance by configuring multiple next-hop proxy servers. The next-hop proxy feature uses round robin load balancing to distribute web traffic across more than one server.

1. On the user interface for Secure Web Gateway, select Policy > Web Policy > Feature Configuration.
2. From the list on the Feature Config page, select Next Hop Proxy > Next Hop Proxy.
3. From the Actions drop-down list, select Clone and Edit.
4. Provide a name for the feature configuration and an optional comment.
5. Click Add Proxy, then configure the following fields:
   • Description — Optionally add a description of the next-hop proxy server.
   • Hostname or IP — Specifies the host name or IP address of the next-hop proxy server.
   • Port — Specifies the port number to use when connecting to the next-hop proxy server.
   • Account Login — Specifies the account name to use when connecting to the next-hop proxy server.
   • Account Password — Specifies the password to use when connecting to the next-hop proxy server.
   • Number of Login Retries — Specifies the maximum number of retries allowed before authentication fails. Default: 1
   • Seconds Between Retries — Specifies the minimum number of seconds allowed between retries.
     Authentication fails when the time between retries is less than the specified minimum. Default: 10
   • Use persistent connections — When selected, this option improves HTTP communications.
6. Click Save.
   
   The next-hop proxy server configuration is saved. Optionally configure and add another next-hop proxy server to the next-hop proxy servers list.

You can publish saved changes to the cloud now or keep working and publish later.