Hi John, both ICAP patch for squid2 and squid3 are in beta state. Nobody works on ICAP patch for squid2 any more. In the other hand squid3 is actively developed,the bugs fixed and is not so bad. Moreover the squid3 ICAP client is better than ICAP patch for squid2 in many aspects (design,features, stability etc...). If the ICAP client is important for you, and you decide to use squid3 then you must know that maybe there are some problems, because squid3 is still in beta release. You can always help squid developers to solve these problems reporting the bugs at squid3 bugzila (http://www.squid-cache.org/bugs) and providing debugging info (stack traces, logs etc). For your problem maybe you can try some workarounds: 1) bypass proxy for WindowsUpdate only(is it possible using proxycfg ?). 2) If you need caching use a different proxy just for WindowsUpdate (why not a squid2.6 in the same box but in a different port) 3) Maybe the problem is the range requests, try to set: range_offset_limit -1 (but possibly has performance penalty and maybe other problems) But before do any of the above try the latest daily snapshot as Amos suggested or just try to apply the patch for bug 2116, it is possibly related with your problem: http://www.squid-cache.org/bugs/show_bug.cgi?id=2116 http://www.squid-cache.org/bugs/attachment.cgi?id=1506 If you are using a beta or development release, applying patches is not unusual... Regards, Christos John Mok wrote: > Hi all, > > But my problem is that I need ICAP client support in squid 3.0. As been > recommended by Christos Chtsanti, the ICAP support in squid 3.0 is > better and more stable than 2.6 + ICAP patch. In that case, can anyone > advise whether I should go 2.6 + ICAP patch, or squid 3.0 RC1 for > production environment (approx. 300 users). > > Thanks a lot, > > John Mok > >
