Currently access.log records various statistics for the client-side of
things. I was wondering how to enable similar settings for the server
side of things. For example:
Web server <-> Squid proxy <-> Client
access.log provides squid proxy <-> client numbers but I want the web
server <-> squid p
# Define external authentication acl
external_acl_type ldap_group %LOGIN /usr/lib/squid/squid_ldap_group -B
ou=people,dc=yourcompany,ou=com -b ou=Group,dc=yourcompany,dc=com -f
(&(cn=%g)(memberUid=%u))" -h ldap.yourcompany.com
# Define the group
acl somegroup external ldap_group group_you_need_to_
See access.log and write a parser for that. See the FAQ
On 4/18/05, Bob Morrison <[EMAIL PROTECTED]> wrote:
> Hello
>
> I need a very easy way to log what user accesses what URL including date and
> time of access. To make things a little harder, I do not want to install
> Apache on the server.
me by
looking at access.log, I want to see how much of that wait is between
the server and the proxy. Then subtract those two numbers to get an
idea of how much overhead squid has.
Thien
On 4/19/05, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Apr 2005, Thien Vu wrote:
>
> &
n this
machine. But from the example above, we do see several hundred
milliseconds of delay for no obvious reason.
Thanks for any pointers on tracking this down.
Thien
On 4/19/05, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Apr 2005, Thien Vu wrote:
>
> > The respons
On 4/20/05, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 20 Apr 2005, Thien Vu wrote:
>
> > That's what I'm thinking also, but we have nearly 300 acls and a
> > similar number of http_access rules.
>
> Ok.
>
> What kinds of acl
On 4/20/05, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> > The rest are url_regex which involve urls or ports (for the CONNECT)
> > later defined in the http_access rules. So essentially we have a
> > population of users and we want to restrict what they can access
> > depending on what group they
