Web Gateway 7.1.5 Product Guide - McAfee

Next-hop proxies
Web filtering
Supporting functions 6
The appliance can use next-hop proxies for routing requests received from its clients to their
destinations. This section explains how to implement and configure these proxies.
When next-hop proxies are implemented, rules in a corresponding rule set use a module to call proxies
that have been entered onto a list for routing requests.
For example, you can route requests that have internal destinations using internal proxies. IP
addresses of destinations that are internal are then entered onto a list, which the routing rule relies on.
Similarly, there can be a list of internal next-hop proxy servers for use by the rule.
A rule set with rules for using next-hop proxies is not implemented on the appliance after the initial
setup. You can import a rule set from the library and modify it according to your needs or create a rule
set of your own.
When you import a next-hop proxy rule set, a server list is also imported, which is initially empty and
must be filled by you. You can also create more than one list and use these lists for routing in different
situations.
Settings for the next-hop proxy module are mported with a library rule set as well. You can configure
these settings to let the module use a particular next-hop proxy list and to determine the mode of
calling the proxies (round-robin or fail-over).
For more information on modes of calling next-hop proxies, see Next-hop proxy modes.
For information on a rule set, lists, and module settings for next-hop proxies, see Next-Hop Proxy, Lists
for next-hop proxy routing, and Configure next-hop proxy settings.
McAfee Web Gateway 7.1.5 Product Guide 233