Re: [squid-users] Associating a log file name with an acl

This would require a new feature to be implemented. Most likely the
feature to have extensible access logging and include a format
specification for logging the allowing (or denying) ACL name.

--
Henrik Nordstrom
Squid Hacker
David Meleedy wrote:
> 
> We are using proxy_auth, and hence in the access logs, usually we
> have a login "name" from the 407 header put into the log file,
> e.g:
> 137.71.254.7 dmeleedy - [01/Jun/2001:04:33:45 -0400] "GET
> http://www.google.com/ HTTP/1.0" 200 2063 TCP_MISS:FIRST_PARENT_MISS
> 
> However, there are certain programs that do not respond to 407 headers
> but none-the-less use the web.  An example of this is "xquote" which
> will download stock information.  So my thought was to set up an
> acl using the user agent information to allow xquote through.
> 
> e.g.
> acl xquote browser Xquote
> acl password proxy_auth REQUIRED
> http_access allow xquote
> http_access allow password
> http_access deny all
> 
> and this all works fine, but in the log file, I naturally see this:
> 137.71.254.7 - - [01/Jun/2001:04:53:40 -0400] "GET
> http://qs2.cnnfn.com/tq/stockquote? HTTP/1.0" 200 32809
> TCP_MISS:FIRST_PARENT_MISS
> 
> What I would like to do, is assign the login name of this acl to
> "xquote", so what I would see in the log would be this:
> 
> 137.71.254.7 xquote - [01/Jun/2001:04:53:40 -0400] "GET
> http://qs2.cnnfn.com/tq/stockquote? HTTP/1.0" 200 32809
> TCP_MISS:FIRST_PARENT_MISS
> 
> Is there a way to do this already? or is this a feature enhancement
> kind of request?