Cisco Cisco Web Security Appliance S380 User Guide

Page of 784
 
Chapter 9      Working with External Proxies
Routing Traffic to Upstream Proxies
9-2
Cisco IronPort AsyncOS 7.0 for Web User Guide
OL-23079-01
For more information about using Routing Policies to route transactions, see 
. For more information about 
defining external proxies, see 
Routing Traffic to Upstream Proxies
When the Web Proxy does not deliver a response from the cache, it can direct 
client requests directly to the destination server or to an external proxy on the 
network. You use Routing Policies to create rules that indicate when and to where 
to direct transactions. A Routing Policy determines to where to pass the client 
request, either to another proxy (as defined by the proxy group) or to the 
destination server. It addresses the question, “from where to fetch content?” You 
might want to create Routing Policies if you have a highly distributed network.
 shows Routing Policies on the Web Security Manager > Routing 
Policies page.
Figure 9-1
Routing Policies
When you define multiple external proxies in a proxy group, the Web Proxy can 
use load balancing techniques to distribute requests to different proxies defined in 
the group. You can choose the following load balancing techniques:
  •
None (failover). The Web Proxy directs transactions to one external proxy in 
the group. It tries to connect to the proxies in the order they are listed. If one 
proxy cannot be reached, the Web Proxy attempts to connect to the next one 
in the list.
  •
Fewest connections. The Web Proxy keeps track of how many active requests 
are with the different proxies in the group and it directs a transaction to the 
proxy currently servicing the fewest number of connections.