Re: [squid-users] light weight ICAP server that isn't dead :o)

[Alex Rousskov]

On 02/09/2015 04:40 PM, Amos Jeffries wrote:

> You might also look into eCAP. The design intention is that you build an
> eCAP module which can plug into either the c-icap engine for access over
> ICAP


I did not realize c-icap added eCAP support. Christos, is that true? We
are adding eCAP support to Traffic Spicer, but it would be nice to have
an open source ICAP+eCAP option as well!


Thank you,

Alex.

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Yuri Voinov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

http://i.imgur.com/fKAUq66.png

5 c-icap processes is good enough to all office building. On squid box
you can see above.

10.02.15 22:56, Luis Miguel Silva пишет:
> I've already installed it and took a look at it but I didn't want
> to waste time evaluating "5 different solutions" so I asked you
> guys to learn what was, statistically, the most popular choice
> :o).
> 
> How about the performance of i-icap with e-cap on top of it? Its my
> understanding that squid can hook directly into e-cap (which would 
> eliminate the i-cap layer [in case I want to use e-cap]). On the
> other hand, I would have to compile squid with e-cap support (which
> I would rather not have to do)...
> 
> Thoughts?
> 
> Thanks, Luis
> 
> On Tue, Feb 10, 2015 at 9:40 AM, Christos Tsantilas
>  wrote:
> 
>> On 02/10/2015 01:00 AM, Luis Miguel Silva wrote:
>> 
>>> 
>>> The most interesting one seems to be C-ICAP but I don't like
>>> that it hasn't even reached a 1.0 version...
>>> 
>> 
>> If you believe that it is interesting then at least test it to
>> see if it matches your needs.
>> 
>> The version number has to do with its goals and number of
>> implemented features and not with its stability.
>> 
>> Regards, Christos
>> 
>> 
>>> What do you guys recommend I adopt?
>>> 
>>> Thank you, Luis Silva
>>> 
>> ___ squid-users
>> mailing list squid-users@lists.squid-cache.org 
>> http://lists.squid-cache.org/listinfo/squid-users
>> 
> 
> 
> 
> ___ squid-users mailing
> list squid-users@lists.squid-cache.org 
> http://lists.squid-cache.org/listinfo/squid-users
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBAgAGBQJU2jlmAAoJENNXIZxhPexGkN0IAMapdc/Fs5jlQTvih7JB1atT
y0s5xUCWuYk+u9K8cVFnyKOOZ7Hoe9xKTmZyisbZ5T3xsKFeqnB8TcdbFEO6T6sm
VYaRYOS47xP0Hb0Cwtt3Cw2ufB2GkbwR67yafuADfQTDyrr20knA8BMz8B5fiah/
oxg6kSM9IFrFAr5Wnom74JLnp3mDwrX7ETD0pv6bX6ZfDY6wfhyZLtMxMeA7bFHl
q+wJq3WpGsLoZ3GQ6pSECAksIl8mUd9ZAME/x6MLnHhy5OvDFEaTgVuE+NTf00f7
W3HJP/OWmBvXRkMFq0UEMoBpnUVrE4q2/YuCt9hkahrWKY7UD81Yv1tOF8idt5Q=
=coB+
-END PGP SIGNATURE-
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Yuri Voinov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



10.02.15 22:56, Luis Miguel Silva пишет:
> I've already installed it and took a look at it but I didn't want
> to waste time evaluating "5 different solutions" so I asked you
> guys to learn what was, statistically, the most popular choice
> :o).
C-ICAP and eCAP.

That's all.

> 
> How about the performance of i-icap with e-cap on top of it?

I see no difference.

> Its my understanding that squid can hook directly into e-cap (which
> would eliminate the i-cap layer [in case I want to use e-cap]). On
> the other hand, I would have to compile squid with e-cap support
> (which I would rather not have to do)...

This is no problem and took approx 30 minutes. With two coffee breaks. :)

> 
> Thoughts?
> 
> Thanks, Luis
> 
> On Tue, Feb 10, 2015 at 9:40 AM, Christos Tsantilas
>  wrote:
> 
>> On 02/10/2015 01:00 AM, Luis Miguel Silva wrote:
>> 
>>> 
>>> The most interesting one seems to be C-ICAP but I don't like
>>> that it hasn't even reached a 1.0 version...
>>> 
>> 
>> If you believe that it is interesting then at least test it to
>> see if it matches your needs.
>> 
>> The version number has to do with its goals and number of
>> implemented features and not with its stability.
>> 
>> Regards, Christos
>> 
>> 
>>> What do you guys recommend I adopt?
>>> 
>>> Thank you, Luis Silva
>>> 
>> ___ squid-users
>> mailing list squid-users@lists.squid-cache.org 
>> http://lists.squid-cache.org/listinfo/squid-users
>> 
> 
> 
> 
> ___ squid-users mailing
> list squid-users@lists.squid-cache.org 
> http://lists.squid-cache.org/listinfo/squid-users
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBAgAGBQJU2jjuAAoJENNXIZxhPexGL/8IAJtwFrMoCFkeoSry2lN9sUHK
o0/6r2EbY/VL6Fqt/lP9AOH9iOcEnh/XgAjSqsL6Pi+zworeVVgBIhrEzSpsALie
/5Eqjsy6yZR71MHzbkVeigNcHNlTVpB5JH9fsvmXCRJ4VT/UhI1eyuuQvwa1CFes
pV1sn105eMyoeF8btRuTLlIylbl+AY1TyySWcgtEnII0DcZwnsIRofOokV0SS6+8
GJGhnrKItk28zOJENMPB9WcetIPyggH7W6/EfNmB0l9SuEQNLCk71xGgMHH1ba+x
1aN42SSefeM2V9XXxWuy/+LkEDrsAX2ifmRcUdiopJ2RPd96g+PIE2mxeE6q82g=
=c3p5
-END PGP SIGNATURE-
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Luis Miguel Silva]

I've already installed it and took a look at it but I didn't want to waste
time evaluating "5 different solutions" so I asked you guys to learn what
was, statistically, the most popular choice :o).

How about the performance of i-icap with e-cap on top of it?
Its my understanding that squid can hook directly into e-cap (which would
eliminate the i-cap layer [in case I want to use e-cap]). On the other
hand, I would have to compile squid with e-cap support (which I would
rather not have to do)...

Thoughts?

Thanks,
Luis

On Tue, Feb 10, 2015 at 9:40 AM, Christos Tsantilas 
wrote:

> On 02/10/2015 01:00 AM, Luis Miguel Silva wrote:
>
>>
>> The most interesting one seems to be C-ICAP but I don't like that it
>> hasn't even reached a 1.0 version...
>>
>
> If you believe that it is interesting then at least test it to see if it
> matches your needs.
>
> The version number has to do with its goals and number of implemented
> features and not with its stability.
>
> Regards,
>Christos
>
>
>> What do you guys recommend I adopt?
>>
>> Thank you,
>> Luis Silva
>>
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Christos Tsantilas]

On 02/10/2015 01:00 AM, Luis Miguel Silva wrote:


The most interesting one seems to be C-ICAP but I don't like that it
hasn't even reached a 1.0 version...


If you believe that it is interesting then at least test it to see if it 
matches your needs.


The version number has to do with its goals and number of implemented 
features and not with its stability.


Regards,
   Christos



What do you guys recommend I adopt?

Thank you,
Luis Silva

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Yuri Voinov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Script solution is not scalable.

C-icap written on C.

10.02.15 19:30, Alejandro Martinez пишет:
> Hi all
> 
> there is an interesting project here
> (https://github.com/netom/pyicap) with some examples about
> implementing an Icap Server
> 
> 
> 2015-02-10 5:21 GMT-02:00 Yuri Voinov :
> 
>> 
>> 10.02.15 5:40, Amos Jeffries пишет:
>> 
>>> On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
>>> 
 Dear all,
 
 I'm looking for a light weight (opensource) ICAP server
 project that isn't dead. I need to create some custom content
 filters but, I'm having a hard time finding an ICAP server
 that is being actively worked on...
 
 The ICAP servers you are looking at are framework servers
 that "just"
>>> decode the on-wire protocol and pass it to a plugin module, and
>>> reverse that for the results. That is all they have to do and
>>> its quite simple, the protocol itself is 12 years old. So you
>>> wont really see huge amounts of ongoing change in any of them.
>>> 
>>> Theres a whole other category of ICAP server, such as AV
>>> vendors. They get a lot more active turnover on their software,
>>> but are all about custom integration for the filtering activity
>>> they do rather than generic plugin engines. And again most of
>>> the code churn is in the filtering parts not the ICAP bits.
>>> 
>>> 
>>> In the squid wiki , I was able to find the following
 ICAP server implementations: - C-ICAP
  -- lates release was in
 October 2014 (which is pretty good) but the latest version is
 0.3.5. *How stable is it?*
 
>>> Stable enougn. Used in my production over half year.
>> 
>>> - Traffic Spicer 
 -- Squid's docs point to this page
  but I couldn't even
 figure out where to download it or find any documentation for
 it. - ICAP-Server  --
 latest version for it is 1.2.1 but it is dated from October
 30, 2002. - POESIA  -- this
 one points to a German page that doesn't seem to have
 anything to do with ICAP... - GreasySpoon
  -- this one seems to
 have been discontinued
 
 The most interesting one seems to be C-ICAP but I don't like
 that it hasn't even reached a 1.0 version...
 
 What do you guys recommend I adopt?
 
 c-icap.
>>> 
>> Agreed. This project alive and software works perfectly.
>> 
>>> 
>>> Though I have to disclaim a slight bias. The c-icap author is
>>> one of our more active Squid developers.
>>> 
>>> 
>>> You might also look into eCAP. The design intention is that you
>>> build an eCAP module which can plug into either the c-icap
>>> engine for access over ICAP or be loaded by Squid for faster
>>> processing directly on the HTTP traffic flow.
>>> 
>> It uses a bit more difficult than c-icap, but very fast.
>> 
>> 
>>> Amos ___ 
>>> squid-users mailing list squid-users@lists.squid-cache.org 
>>> http://lists.squid-cache.org/listinfo/squid-users
>>> 
>> 
>> ___ squid-users
>> mailing list squid-users@lists.squid-cache.org 
>> http://lists.squid-cache.org/listinfo/squid-users
>> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBAgAGBQJU2ghRAAoJENNXIZxhPexGn3MIALnRZJzJ8xRohs5cM7VxI6D5
omC0GZoaFOQiBPNx1AJpoC1a1utwMAQq3DJWUdO2VyfDYgrDEUPhxBoXWn0ro41v
YgVT1MUwslGdOsy+G3ZdW03l30EPftI3NxPH64JVPxk8689kVV/IC54WIw+5P70i
GVN4D4KXgJ0bv+FVxZddkpyLPGTLdnXOEHUizZbvXl/f/Yf0pQyV03G8iIw1kaLu
cwK81lUtK2OIvF25HI18N0s3gO9LsqyDvRyoF5qrLPsz3kxUaTotK6S5/tqNyJbb
15ntXv2rjkLk5lW0gpZngcfmyZ297YkyfUOifkABJamCtGgMD5uazeeGxJ7PZJU=
=I2gC
-END PGP SIGNATURE-
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Alejandro Martinez]

Hi all

there is an interesting project here (https://github.com/netom/pyicap) with
some examples about implementing an Icap Server


2015-02-10 5:21 GMT-02:00 Yuri Voinov :

>
> 10.02.15 5:40, Amos Jeffries пишет:
>
>> On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
>>
>>> Dear all,
>>>
>>> I'm looking for a light weight (opensource) ICAP server project that
>>> isn't
>>> dead.
>>> I need to create some custom content filters but, I'm having a hard time
>>> finding an ICAP server that is being actively worked on...
>>>
>>>  The ICAP servers you are looking at are framework servers that "just"
>> decode the on-wire protocol and pass it to a plugin module, and reverse
>> that for the results. That is all they have to do and its quite simple,
>> the protocol itself is 12 years old. So you wont really see huge amounts
>> of ongoing change in any of them.
>>
>> Theres a whole other category of ICAP server, such as AV vendors. They
>> get a lot more active turnover on their software, but are all about
>> custom integration for the filtering activity they do rather than
>> generic plugin engines. And again most of the code churn is in the
>> filtering parts not the ICAP bits.
>>
>>
>>  In the squid wiki >> Features/ICAP#ICAP_Servers>,
>>> I was able to find the following ICAP server implementations:
>>> - C-ICAP 
>>> -- lates release was in October 2014 (which is pretty good) but the
>>> latest
>>> version is 0.3.5. *How stable is it?*
>>>
>> Stable enougn. Used in my production over half year.
>
>> - Traffic Spicer 
>>> -- Squid's docs point to this page >> factory.com/>
>>> but I couldn't even figure out where to download it or find any
>>> documentation for it.
>>> - ICAP-Server 
>>> -- latest version for it is 1.2.1 but it is dated from October 30, 2002.
>>> - POESIA 
>>> -- this one points to a German page that doesn't seem to have anything to
>>> do with ICAP...
>>> - GreasySpoon 
>>> -- this one seems to have been discontinued
>>>
>>> The most interesting one seems to be C-ICAP but I don't like that it
>>> hasn't
>>> even reached a 1.0 version...
>>>
>>> What do you guys recommend I adopt?
>>>
>>>  c-icap.
>>
> Agreed. This project alive and software works perfectly.
>
>>
>> Though I have to disclaim a slight bias. The c-icap author is one of our
>> more active Squid developers.
>>
>>
>> You might also look into eCAP. The design intention is that you build an
>> eCAP module which can plug into either the c-icap engine for access over
>> ICAP or be loaded by Squid for faster processing directly on the HTTP
>> traffic flow.
>>
> It uses a bit more difficult than c-icap, but very fast.
>
>
>> Amos
>> ___
>> squid-users mailing list
>> squid-users@lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
>>
>
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Yuri Voinov]

10.02.15 5:40, Amos Jeffries пишет:

On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:

Dear all,

I'm looking for a light weight (opensource) ICAP server project that isn't
dead.
I need to create some custom content filters but, I'm having a hard time
finding an ICAP server that is being actively worked on...


The ICAP servers you are looking at are framework servers that "just"
decode the on-wire protocol and pass it to a plugin module, and reverse
that for the results. That is all they have to do and its quite simple,
the protocol itself is 12 years old. So you wont really see huge amounts
of ongoing change in any of them.

Theres a whole other category of ICAP server, such as AV vendors. They
get a lot more active turnover on their software, but are all about
custom integration for the filtering activity they do rather than
generic plugin engines. And again most of the code churn is in the
filtering parts not the ICAP bits.



In the squid wiki ,
I was able to find the following ICAP server implementations:
- C-ICAP 
-- lates release was in October 2014 (which is pretty good) but the latest
version is 0.3.5. *How stable is it?*

Stable enougn. Used in my production over half year.

- Traffic Spicer 
-- Squid's docs point to this page 
but I couldn't even figure out where to download it or find any
documentation for it.
- ICAP-Server 
-- latest version for it is 1.2.1 but it is dated from October 30, 2002.
- POESIA 
-- this one points to a German page that doesn't seem to have anything to
do with ICAP...
- GreasySpoon 
-- this one seems to have been discontinued

The most interesting one seems to be C-ICAP but I don't like that it hasn't
even reached a 1.0 version...

What do you guys recommend I adopt?


c-icap.

Agreed. This project alive and software works perfectly.


Though I have to disclaim a slight bias. The c-icap author is one of our
more active Squid developers.


You might also look into eCAP. The design intention is that you build an
eCAP module which can plug into either the c-icap engine for access over
ICAP or be loaded by Squid for faster processing directly on the HTTP
traffic flow.

It uses a bit more difficult than c-icap, but very fast.


Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Luis Miguel Silva]

Cool, thanks for sharing!

Could you also share your icap-filter/ directory (namely,
icap-filter/html/*, icap-filter/request-filters and
icap-filter/content-filters)?

Thanks,
Luis

On Mon, Feb 9, 2015 at 7:35 PM, James Leu  wrote:

> Not sure if this is usefull to anyone.  Here is a simple perl server that
> tries to implement ICAP.  YMMV (attached)
>
> On Mon, Feb 09, 2015 at 05:18:36PM -0700, Luis Miguel Silva wrote:
> > Thanks Amos.
> >
> > Well, that's exactly what I'm going to need to develop too (the plugin
> > part), I just found it weird that the C-ICAP service was still version
> > 0.3.5, even though it was really old. If it is mature, I would expect it
> to
> > get to v1.0 and cease development :o)
> >
> > So...what one would you recommend if you wanted to easily create
> > (lightweight) custom filtering capabilities?
> > I'm very inclined to adopt c-icap. Thoughts?
> >
> > Thanks,
> > Luis
> >
> > On Mon, Feb 9, 2015 at 4:40 PM, Amos Jeffries 
> wrote:
> >
> > > On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
> > > > Dear all,
> > > >
> > > > I'm looking for a light weight (opensource) ICAP server project that
> > > isn't
> > > > dead.
> > > > I need to create some custom content filters but, I'm having a hard
> time
> > > > finding an ICAP server that is being actively worked on...
> > > >
> > >
> > > The ICAP servers you are looking at are framework servers that "just"
> > > decode the on-wire protocol and pass it to a plugin module, and reverse
> > > that for the results. That is all they have to do and its quite simple,
> > > the protocol itself is 12 years old. So you wont really see huge
> amounts
> > > of ongoing change in any of them.
> > >
> > > Theres a whole other category of ICAP server, such as AV vendors. They
> > > get a lot more active turnover on their software, but are all about
> > > custom integration for the filtering activity they do rather than
> > > generic plugin engines. And again most of the code churn is in the
> > > filtering parts not the ICAP bits.
> > >
> > >
> > > > In the squid wiki <
> > > http://wiki.squid-cache.org/Features/ICAP#ICAP_Servers>,
> > > > I was able to find the following ICAP server implementations:
> > > > - C-ICAP 
> > > > -- lates release was in October 2014 (which is pretty good) but the
> > > latest
> > > > version is 0.3.5. *How stable is it?*
> > > > - Traffic Spicer 
> > > > -- Squid's docs point to this page <
> > > http://spicer.measurement-factory.com/>
> > > > but I couldn't even figure out where to download it or find any
> > > > documentation for it.
> > > > - ICAP-Server 
> > > > -- latest version for it is 1.2.1 but it is dated from October 30,
> 2002.
> > > > - POESIA 
> > > > -- this one points to a German page that doesn't seem to have
> anything to
> > > > do with ICAP...
> > > > - GreasySpoon 
> > > > -- this one seems to have been discontinued
> > > >
> > > > The most interesting one seems to be C-ICAP but I don't like that it
> > > hasn't
> > > > even reached a 1.0 version...
> > > >
> > > > What do you guys recommend I adopt?
> > > >
> > >
> > > c-icap.
> > >
> > > Though I have to disclaim a slight bias. The c-icap author is one of
> our
> > > more active Squid developers.
> > >
> > >
> > > You might also look into eCAP. The design intention is that you build
> an
> > > eCAP module which can plug into either the c-icap engine for access
> over
> > > ICAP or be loaded by Squid for faster processing directly on the HTTP
> > > traffic flow.
> > >
> > > Amos
> > > ___
> > > squid-users mailing list
> > > squid-users@lists.squid-cache.org
> > > http://lists.squid-cache.org/listinfo/squid-users
> > >
>
>
> --
> James R. Leu
> j...@mindspring.com
>
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[James Leu]

Not sure if this is usefull to anyone.  Here is a simple perl server that
tries to implement ICAP.  YMMV (attached)

On Mon, Feb 09, 2015 at 05:18:36PM -0700, Luis Miguel Silva wrote:
> Thanks Amos.
> 
> Well, that's exactly what I'm going to need to develop too (the plugin
> part), I just found it weird that the C-ICAP service was still version
> 0.3.5, even though it was really old. If it is mature, I would expect it to
> get to v1.0 and cease development :o)
> 
> So...what one would you recommend if you wanted to easily create
> (lightweight) custom filtering capabilities?
> I'm very inclined to adopt c-icap. Thoughts?
> 
> Thanks,
> Luis
> 
> On Mon, Feb 9, 2015 at 4:40 PM, Amos Jeffries  wrote:
> 
> > On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
> > > Dear all,
> > >
> > > I'm looking for a light weight (opensource) ICAP server project that
> > isn't
> > > dead.
> > > I need to create some custom content filters but, I'm having a hard time
> > > finding an ICAP server that is being actively worked on...
> > >
> >
> > The ICAP servers you are looking at are framework servers that "just"
> > decode the on-wire protocol and pass it to a plugin module, and reverse
> > that for the results. That is all they have to do and its quite simple,
> > the protocol itself is 12 years old. So you wont really see huge amounts
> > of ongoing change in any of them.
> >
> > Theres a whole other category of ICAP server, such as AV vendors. They
> > get a lot more active turnover on their software, but are all about
> > custom integration for the filtering activity they do rather than
> > generic plugin engines. And again most of the code churn is in the
> > filtering parts not the ICAP bits.
> >
> >
> > > In the squid wiki <
> > http://wiki.squid-cache.org/Features/ICAP#ICAP_Servers>,
> > > I was able to find the following ICAP server implementations:
> > > - C-ICAP 
> > > -- lates release was in October 2014 (which is pretty good) but the
> > latest
> > > version is 0.3.5. *How stable is it?*
> > > - Traffic Spicer 
> > > -- Squid's docs point to this page <
> > http://spicer.measurement-factory.com/>
> > > but I couldn't even figure out where to download it or find any
> > > documentation for it.
> > > - ICAP-Server 
> > > -- latest version for it is 1.2.1 but it is dated from October 30, 2002.
> > > - POESIA 
> > > -- this one points to a German page that doesn't seem to have anything to
> > > do with ICAP...
> > > - GreasySpoon 
> > > -- this one seems to have been discontinued
> > >
> > > The most interesting one seems to be C-ICAP but I don't like that it
> > hasn't
> > > even reached a 1.0 version...
> > >
> > > What do you guys recommend I adopt?
> > >
> >
> > c-icap.
> >
> > Though I have to disclaim a slight bias. The c-icap author is one of our
> > more active Squid developers.
> >
> >
> > You might also look into eCAP. The design intention is that you build an
> > eCAP module which can plug into either the c-icap engine for access over
> > ICAP or be loaded by Squid for faster processing directly on the HTTP
> > traffic flow.
> >
> > Amos
> > ___
> > squid-users mailing list
> > squid-users@lists.squid-cache.org
> > http://lists.squid-cache.org/listinfo/squid-users
> >


-- 
James R. Leu
j...@mindspring.com


icap.pl
Description: Perl program
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Luis Miguel Silva]

Thanks Amos.

Well, that's exactly what I'm going to need to develop too (the plugin
part), I just found it weird that the C-ICAP service was still version
0.3.5, even though it was really old. If it is mature, I would expect it to
get to v1.0 and cease development :o)

So...what one would you recommend if you wanted to easily create
(lightweight) custom filtering capabilities?
I'm very inclined to adopt c-icap. Thoughts?

Thanks,
Luis

On Mon, Feb 9, 2015 at 4:40 PM, Amos Jeffries  wrote:

> On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
> > Dear all,
> >
> > I'm looking for a light weight (opensource) ICAP server project that
> isn't
> > dead.
> > I need to create some custom content filters but, I'm having a hard time
> > finding an ICAP server that is being actively worked on...
> >
>
> The ICAP servers you are looking at are framework servers that "just"
> decode the on-wire protocol and pass it to a plugin module, and reverse
> that for the results. That is all they have to do and its quite simple,
> the protocol itself is 12 years old. So you wont really see huge amounts
> of ongoing change in any of them.
>
> Theres a whole other category of ICAP server, such as AV vendors. They
> get a lot more active turnover on their software, but are all about
> custom integration for the filtering activity they do rather than
> generic plugin engines. And again most of the code churn is in the
> filtering parts not the ICAP bits.
>
>
> > In the squid wiki <
> http://wiki.squid-cache.org/Features/ICAP#ICAP_Servers>,
> > I was able to find the following ICAP server implementations:
> > - C-ICAP 
> > -- lates release was in October 2014 (which is pretty good) but the
> latest
> > version is 0.3.5. *How stable is it?*
> > - Traffic Spicer 
> > -- Squid's docs point to this page <
> http://spicer.measurement-factory.com/>
> > but I couldn't even figure out where to download it or find any
> > documentation for it.
> > - ICAP-Server 
> > -- latest version for it is 1.2.1 but it is dated from October 30, 2002.
> > - POESIA 
> > -- this one points to a German page that doesn't seem to have anything to
> > do with ICAP...
> > - GreasySpoon 
> > -- this one seems to have been discontinued
> >
> > The most interesting one seems to be C-ICAP but I don't like that it
> hasn't
> > even reached a 1.0 version...
> >
> > What do you guys recommend I adopt?
> >
>
> c-icap.
>
> Though I have to disclaim a slight bias. The c-icap author is one of our
> more active Squid developers.
>
>
> You might also look into eCAP. The design intention is that you build an
> eCAP module which can plug into either the c-icap engine for access over
> ICAP or be loaded by Squid for faster processing directly on the HTTP
> traffic flow.
>
> Amos
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] light weight ICAP server that isn't dead :o)

[Amos Jeffries]

On 10/02/2015 12:00 p.m., Luis Miguel Silva wrote:
> Dear all,
> 
> I'm looking for a light weight (opensource) ICAP server project that isn't
> dead.
> I need to create some custom content filters but, I'm having a hard time
> finding an ICAP server that is being actively worked on...
> 

The ICAP servers you are looking at are framework servers that "just"
decode the on-wire protocol and pass it to a plugin module, and reverse
that for the results. That is all they have to do and its quite simple,
the protocol itself is 12 years old. So you wont really see huge amounts
of ongoing change in any of them.

Theres a whole other category of ICAP server, such as AV vendors. They
get a lot more active turnover on their software, but are all about
custom integration for the filtering activity they do rather than
generic plugin engines. And again most of the code churn is in the
filtering parts not the ICAP bits.


> In the squid wiki ,
> I was able to find the following ICAP server implementations:
> - C-ICAP 
> -- lates release was in October 2014 (which is pretty good) but the latest
> version is 0.3.5. *How stable is it?*
> - Traffic Spicer 
> -- Squid's docs point to this page 
> but I couldn't even figure out where to download it or find any
> documentation for it.
> - ICAP-Server 
> -- latest version for it is 1.2.1 but it is dated from October 30, 2002.
> - POESIA 
> -- this one points to a German page that doesn't seem to have anything to
> do with ICAP...
> - GreasySpoon 
> -- this one seems to have been discontinued
> 
> The most interesting one seems to be C-ICAP but I don't like that it hasn't
> even reached a 1.0 version...
> 
> What do you guys recommend I adopt?
> 

c-icap.

Though I have to disclaim a slight bias. The c-icap author is one of our
more active Squid developers.


You might also look into eCAP. The design intention is that you build an
eCAP module which can plug into either the c-icap engine for access over
ICAP or be loaded by Squid for faster processing directly on the HTTP
traffic flow.

Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users