Re: Access Control

In <199608190238.TAA08176@nlanr.net>, on 08/18/96 at 07:38 PM,
   Duane Wessels <wessels@nlanr.net> said:

>>Secondally, can the squid.conf file read another file (eg acl.list) for
>>it's ACL commands? I would rather do this incase of something decided to
>>trash the config file (which, knowing my luck, it would *8-]

>It can't yet read ACL's from another file. (It can read 'local_domain'
>entries from a file, but that is the only one at the moment).

>>Thirdly, is there a limit to the size of an ACL command? In the followin
>>command set the domain line could contain a couple of hundred sites
>>(potentially) Is this a problem?

>Yes it will be a problem. You should break it into multiple 'acl' lines
>with different names. You can't have more than 1024 characters per line
>in the config file.

Hmmm... that will make it harder.

So I should define one acl and domain name to each session I suppose...

so it would look like:

acl session1 domain .one.com .two.com .three.com
http_access deny ourschool session1
acl session2 domain .four.com .five.com .six.com
http_access deny ourschool session2

In the simplest form...

Given that a couple of hundred sites will be added eventually... we are
going to get a looong config file. What are the performance consequences
here? (I assume negligable and highly dependant on server speed...) but is
there any limits I am going to hit in a hurry?

Obviously an imediate performance gain would be to aggregate the
http_access lines.. but again I am going to hit the 1024 limit real
fast...

Possible upgrade feature? *8-]

Regards and Salutations,

Mikel

-- 
-----------------------------------------------------------
Mikel Lindsaar        |  "The dream is the foundation,
mikel@cynet.net.au    |        of our society!" 
-----------------------------------------------------------
Cynet!  The Business ISP!   http://www.cynet.net.au/
-----------------------------------------------------------