> > WCCPv2 is supported in all current Squid (2.6+, 3.0+) > > The squid just needs to be built with --enable-wccpv2 > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10 > Current Beta Squid 3.1.0.1 > Also fully support these two features? 1. Sending the packets squid can not service back to router via GRE tunnel or Layer 2. There are many applications just "borrow" the port 80 and send their own formatted data, they are not HTTP requests at all. Currently squid will only report a "clientTryParseRequest: FD 41 (x.x.x.x:xxxx) Invalid Request" error in cache_log when receiving these packets. 2. Sending packets back according to the ACLs defined in squid.conf. So when customers access some domains or URLs, the request packets can be returned back and then go out directly. A bit like the redirect-list defined on router, but we can't write domains or URLs in router's access-list.
