Transparent interception with policy-based routing

Instead of the WCCP protocol, you can use the policy routing capabilities of a router to send traffic to Content Gateway. WCCP or a Layer 4 switch are generally preferable to this configuration because policy-based routing has a performance impact on the router, and policy-based routing does not support load balancing or heartbeat messaging.

• All client Internet traffic is sent to a router that feeds Content Gateway.
• The router sends port 80 (HTTP) traffic to the proxy and sends the remaining traffic to the next hop router.
• The ARM redirects intercepted requests to Content Gateway.
• Web objects to be served transparently are redirected by the ARM on the return path to the client, so that the documents appear to have come from the origin server.

A Content Gateway cluster with virtual IP failover adds reliability; if one node fails, another node can take up its transparency requests. See Virtual IP failover.