About squid3 and icap logs, there is an icap logging patch maintained by
Alex Rousskov:
https://code.launchpad.net/~rousskov/squid/IcapLog3p0
It has many options including options for logging icap headers.
The c-icap does not have a good logging system. But maybe you can modify
its code, write your own logging modules or pay someone to do. Please
ask about c-icap in c-icap-users mailing list.
Regards,
Christos
Anuj Singh wrote:
Thanks a lot Christos Tsantilas,
It worked!.
Another thing I want to ask is, I wonder if we can decrase the size of
c-icap logs as well as get some more details under c-icap to corelate
c-icap server/access logs with squid or dansguardian logs and easily
get the machine IP from which virus threat url was accessed?
Currently a virus url access throws a 404 page on client machine, can
we send some reason to client machine instead of 404 page?
At the moment I am using a cron entry to keep cleaning the excessive logs.
Thanks & Regards
Anuj Singh
