Re: [squid-users] Is there ICAP evidence log in any log files?

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 11 Feb 2010 11:07:17 +1300

On Wed, 10 Feb 2010 10:51:16 -0600, Luis Daniel Lucio Quiroz
<luis.daniel.lucio_at_gmail.com> wrote:
> Le Mardi 9 Février 2010 22:57:58, Amos Jeffries a écrit :
>> Henrik Nordström wrote:
>> > tis 2010-02-09 klockan 15:18 -0600 skrev Luis Daniel Lucio Quiroz:
>> >> Le Mercredi 30 Juillet 2008 22:24:35, Henrik Nordstrom a écrit :
>> >>> On tor, 2008-07-31 at 11:26 +0900, S.KOBAYASHI wrote:
>> >>>> Hello developer,
>> >>>>
>> >>>> I'm looking for the evidence for accessing ICAP server. Is there
its
>> >>>> log in any log files such as access.log, cache.log?
>> >>>
>> >>> The ICAP server should have logs of it's own.
>> >>>
>> >>> There is no information in the Squid logs on which iCAP servers
were
>> >>> used for the request/response.
>> >>>
>> >>> Regards
>> >>> Henrik
>> >>
>> >> I wonder if using squidclient mngr:xxXX we could see some info
about
>> >> icap, where?
>> >
>> > Seems not.
>> >
>> > You can however increase the debug level of section 93 to have ICAP
>> > spew
>> > out lots of information in cache.log.
>> >
>> > debug_options ALL,1 93,5
>> >
>> > should do the trick I think.
>> >
>> > Regards
>> > Henrik
>>
>> Squid-3.1 and later provide some little ICAP service logging in
>> access.log.
>> http://www.squid-cache.org/Doc/config/logformat/
>>
>>
>> Amos
> Do you think we could backport that logging in access.log capabilitie.
I
> may
> do that but just tellme what file to backport.
>
> TIA
>
> LD

It was quite a major change. For only a small benefit. It won't be done
upstream sorry.

3.1 is out as stable in less than 60 days though if everything goes to
plan.
(one blocker bug to go. Major, but solo).

Amos
Received on Wed Feb 10 2010 - 22:07:20 MST

This archive was generated by hypermail 2.2.0 : Wed Feb 24 2010 - 12:00:06 MST