I would like to subscribe to squid mailing list

2006-05-29 Thread Moshe Beeri
Hi, I am Moshe Beeri, and I work for PureSight (www.PureSight.com) Recently I applied the ICAP patch into squid 2.5 stable 10, We at PureSight are using ICAP for content filtering and we are using our own server, as I worked with squid ICAP I realized that the support for content filtering is

context data for squid ICAP patched

2006-05-29 Thread Moshe Beeri
Hi all squids, Background information: I am implementing an extension to squid ICAP client based upon ICAP Patch and squid 2.5 STABLE 10. The squid ICAP client does not support Content Filtering the way we at PureSight.com using it. The ICAP protocol is defined to support also Content Filtering

Re: context data for squid ICAP patched

2006-05-29 Thread Tsantilas Christos
Hi Beeri, Maybe you do not need to modify the squid-icap code to support your model. I think that the correct implementation of your problem using squid-icap is: 1) An http request come into the squid. Squid sends the reqmod request to the icap server and server clasifies the request: a) In

Re: Squid-2.6 update

2006-05-29 Thread Henrik Nordstrom
Please keep discussions on the mailinglist, thanks. Well, then I againg suggest cosmetic changes for C++ compatibility: ushort class; to ushort _class; in cache_cf.c int class; to int _class; in delay_pools.c unsigned char *class; to unsigned char *_class;

Re: making cache manager presence/registration optional

2006-05-29 Thread Gonzalo Arana
Hi, I believe there is a little problem with this. If store digest is not enabled. I get: store_digest.cc: In function `void storeDigestRegisterWithCacheManager(CacheManager)': store_digest.cc:135: error: `registerAction' undeclared (first use this function) store_digest.cc:135: error:

Re: making cache manager presence/registration optional

2006-05-29 Thread Gonzalo Arana
I've just noticed these other issues: 1) epoll is enabled 2) xprof is not used 3) delay pools are not enabled Attached is a proposal for this (supersedes my previous patch). Regards, On 5/29/06, Gonzalo Arana [EMAIL PROTECTED] wrote: Hi, I believe there is a little problem with this. If

RE: context data for squid ICAP patched

2006-05-29 Thread Moshe Beeri
Hi Christos, Thank you for your help, but you suggestion is not secure nor best perform, Please read my other remarks below. Now that I read the question again I see it is not clear enough, I will ask again. I would like squid ICAP client to do the logic for couple of reasons, 1. Security -

RE: context data for squid ICAP patched

2006-05-29 Thread Tsantilas Christos
Hi Beeri, 1. Security - Origin sever might change the replied http header and add the X-MY-SCANNER: Allow it self, and bypass the content filter, In that case I would not be able to prevent kids from viewing un honest pages :-( Yes this problem exists. I am just refering it as

Re: making cache manager presence/registration optional

2006-05-29 Thread Robert Collins
On Mon, 2006-05-29 at 11:13 -0300, Gonzalo Arana wrote: I've just noticed these other issues: 1) epoll is enabled 2) xprof is not used 3) delay pools are not enabled Attached is a proposal for this (supersedes my previous patch). Thanks, applied. Rob -- GPG key available at:

2.6.PRE1 is out the door

2006-05-29 Thread Henrik Nordstrom
The 2.6.PRE1 release has been shipped. http://www.squid-cache.org/Versions/v2/2.6/ Have a good feeling about it in general, but much testing remains. Open issues where you can help: - WCCPv2 workaround for Linux/IOS when having multiple routers. Should use one connected socket per router.

Wccp2 config cleanup

2006-05-29 Thread Steven Wilton
Here's a small patch to wccp2 in squid 2.6. It fixes a difference between the code and the documentation in the default squid conf (proto= compared to protocol=). It also removes the ports_defined config variable, enables the flag when ports are actually defined and checks to see that this flag

Re: 2.6.PRE1 is out the door

2006-05-29 Thread Adrian Chadd
On Tue, May 30, 2006, Henrik Nordstrom wrote: - Some benchmarking is needed to see if comm_poll is really worth to keep, or if comm_select is actually better. The current comm_poll implementation looks extremely inefficient (same as it always been in 2.x).. Poll should be better - it'll be