Installation guide

Another type of clustering supported by the Content Gateway is cross-cache
clustering, a complex proxy deployment that allows any node in a proxy cluster to
share cache contents across the other nodes. This type of cluster also includes the
configuration sharing feature in management clustering previously described. As Web
content becomes increasingly dynamic, content caching becomes less effective at
enhancing system performance. Cross-cache clustering is not a recommended
deployment for Websense Content Gateway.
Clusters that are deployed with load balancing schemes that distribute requests based
on origin server IP or hostname (for example, with WCCP) cannot benefit from cross-
cache clustering, because 2 caches never receive requests for the same content. You
should not use cross-cache clustering with WCCP.
See Websense Content Gateway Online Help (in the chapter titled Clusters) for
information about configuring proxy clusters.
IP spoofing
When enabled, the IP spoofing feature directs the proxy to use the client IP address
when establishing a connection to an origin server, rather than the proxy’s IP address.
With this option, a request appears to be from the client, not the proxy. IP spoofing is
intended for transparent proxy deployments. You should note that if IP spoofing is
implemented, the client IP address is used for all HTTP requests in both transparent
and explicit proxy deployments.
You might want to implement this feature, for example, if an upstream network device
is used to log HTTP traffic, perform authentication, or access controls based on the
client IP address.
For information about how to enable IP spoofing, see the chapter titled Transparent
Proxy Caching and ARM in Websense Content Gateway Online Help.
Note
If you enable HTTPS content inspection (SSL) in a
management cluster, you must configure each node
manually for all SSL features.
Note
When SSL decryption is enabled, HTTPS traffic does not
support IP spoofing.