Re: FW: [squid-users] Access Lists

2001/10/31 14:57:50| aclParseAclLine: ACL 'jkane' already exists with
different type, skipping.

Trial and error never hurts...

Peter Smith

Paul Harlow wrote:

>Oops...meant to send to the list!
>
>-----Original Message-----
>From: Paul Harlow
>Sent: Wednesday, October 31, 2001 11:12 AM
>To: 'Henrik Nordstrom'
>Subject: RE: [squid-users] Access Lists
>
>
>So with this in mind could I do the following:
>
>acl jkane src 10.9.1.112/255.255.255.255
>acl jkane dstdom_regex adams
>http_access allow jkane
>
>Instead? Simpler and from what you've stated, if I understand correctly,
>this would do the same thing. Correct?
>
>
>-----Original Message-----
>From: Henrik Nordstrom [mailto:hno@squid-cache.org]
>Sent: Wednesday, October 31, 2001 10:52 AM
>To: Paul Harlow
>Cc: Squid Users (E-mail)
>Subject: Re: [squid-users] Access Lists
>
>
>Paul Harlow wrote:
>
>>acl jkanepc src 10.9.1.112/255.255.255.255
>>This one allows "jkanepc" with a source address of 10.9.1.112...
>>
>
>Not quite. It defines the acl list "jkanepc" that can later be used to
>allow/deny access in http_access.
>
>>acl jkane dstdom_regex adams
>>I'm assuming that the access list name is "jkane" and that this will read
>>anything with the name "adams" in the address field.
>>
>
>Exacly.
>
>>http_access allow jkane jkanepc
>>Finally, this ties the two together if I'm not mistaken. It ties the list
>>"jkane" with the "jkanepc" address, correct?
>>
>
>Sort of.
>
>To be specific it allows the request if it matches both the "jkane" and
>"jkanepc" acl lists.
>
>Regards
>Henrik Nordström
>
Received on Wed Oct 31 2001 - 14:03:40 MST