Installation guide

A comparison of how some activities are handled in explicit and transparent proxy
deployments appears in the following table:
Special Deployment Scenarios
Websense Content Gateway can be deployed in proxy clusters with failover features
that contribute to high availability. The proxy can also be deployed in a chain, either
with other Websense Content Gateway proxies or third-party proxies. This section
describes some examples of these deployment scenarios.
Highly available Web proxy
A highly available Web proxy provides continuous, reliable system operation.
Minimizing system downtime increases user access and productivity.
Proxy high availability may be accomplished via a proxy cluster that uses various
failover contingencies. Such deployments may involve either an explicit or
transparent proxy configuration, load balancing, virtual IP addresses, and a variety of
Activity Explicit Proxy
Deployment
Transparent Proxy
Deployment
Proxy Chain
Client HTTP
request
Direct connection to
proxy by browser to
port 8080 (default)
Redirected to proxy by
network device using
GRE encapsulation or
by rewriting the L2
destination MAC
address to the proxy’s
address
Direct connection to
parent proxy from child
proxy
Exception
management
Exclude site, CIDR,
etc., using browser
configuration
settings and PAC
file settings.
Static or dynamic
bypass rules
Child/parent proxy
configuration rules
Proxy
authentication
Proxy challenge
using 407 Proxy
Authentication
Required code
Challenge using
server-based
authentication scheme
(client is not aware of
proxy)
Proxies in a chain may
share credential
information, or a single
proxy in the chain can
perform authentication.
Redundancy Proxy virtual IP pool
shared across
multiple proxies
WCCP pool with
multiple proxies
Parent/child
configuration points to
proxy virtual IP
addresses.
Proxy
management
Management
clustering
Management
clustering
Management clustering
Load
balancers
Supported N/A Supported