RE: [squid-users] logging of headers after request modification

Yes, I am EXACTLY talking about this...

Or a means to log if an ACL matches of not in true/false (or maybe via notes, which are not fully documented yet on the website).
But then Trunk is definitely not ready for a production envirionment...

So if you can think of something else that may get me this information into the logfile - help would be greatly appreciated...

Martin

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Dienstag, 07. Mai 2013 17:55
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] logging of headers after request modification

On 8/05/2013 2:03 a.m., Martin Sperl wrote:
> Hi!
>
> I have configured squid 3.2.7 logging with the following pattern to log:
>
> logformat xml ...<Via>%{Via}>ha</Via>...
> access_log daemon:/var/logs/squid/access_log.xml xml all
>
> But I have the problem, that the <VIA> fields stay "empty" (actually "-")...
>
> So I wonder why and how I can change that, so that I get the Via header as well...

%>ha logs the header received from the client, after they have been
altered by ICAP, eCAP, or url_rewrite adaptation.

However what you are talking about is the header delivered to the server
or peer. I'm not sure if we have anything which logs that in logformat
codes yet.

Amos

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
Received on Tue May 07 2013 - 16:06:48 MDT