we are replacing our Cisco content engines, which were directing requests to SmartFilter.
The replacement is the McAfee web gateway's.
We are finding that if we set the browser to go direct to the proxy it works.
WCCP redirection is not working reliably at all.
Wondering if others are setul using WCCP for proxy?
version is 18.104.22.168.0 (9319), but it didn't work in the version before that either from what I recall.
we are not authenticating WCCP calls.. this is the 'catch all' when a client is not going to the web gateway via a direct proxy. From prior version of web gateway (version 6) we learned that trying to authenticate the WCCP user was unreliable and prone to problems.
we find that using WCCP will result in requests hanging and not completing. Sometimes it works, most of the time it doesn't.
wondering if it is a product problem.. if you (or others) are successfully using the web gateway v7 using WCCP, I'd like to collaborate to understand what might be amiss here!
We are currently running WCCP mode in Web Gateway 7.0.2. It works fine for us. WCCP is setup in our Cisco ASA firewall to point port 80, 443 to our gateways.
We have two Gateways with are also load balancing with WCCP automatically. (wccp sends out hash buckets)
Authentication also works great. You have to authenticate differently than direct proxy mode.