Search squid archive

Re: logging of headers after request modification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/07/2013 08:03 AM, Martin Sperl wrote:

> 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...

> P.s: I am modifying the VIA header in my config like this under some circumstances:
> request_header_access Via allow CUSTOM_ACL
> request_header_access Via deny all
> request_header_replace Via mypersonalvalue

> The application sees the "expected" value in the Via header, so that
> itself is not an issue - only logging the header is NOT working as
> expected... (it actually only works IF


[http::]>ha logs request headers received by Squid and adapted by
ICAP/eCAP. It does not log request headers sent by Squid. There is
currently no logformat code to log the latter.

If you want to log outgoing Via, your options include:

1) add a logformat code to log outgoing request headers (requires
development);

2) use "note" directive and %note logformat code to log mypersonalvalue
when needed (requires Squid trunk?)

3) move Via manipulation to ICAP/eCAP while disabling Squid's Via
generation (requires writing or adjusting an adaptation service).


HTH,

Alex.





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux