Re: External deny file

From: Michael Fuhr <mfuhr@dont-contact.us>
Date: Mon, 12 Oct 1998 01:06:35 -0600

On Mon, Oct 12, 1998 at 04:12:00PM +1100, Duane Ellery wrote:

> Is it possible to use a seperate file for http_access deny because I have got approx 105 deny lines in the squid.conf file that have to be changed regularly and it takes ages to scroll through when telneting to it.

Your squid.conf file should contain comments on how to define ACLs.
You can define an ACL in a file, then use that ACL with http_access:

    acl allowed-hosts src "/path/to/acl/file"
    http_access allow allowed-hosts

The contents of /path/to/acl/file could be something like this:

    192.168.1.1
    192.168.1.2
    192.168.2.0/24

> Here is an example of what I have:
> # Rooms #
> #MONDAY
> acl mondaymorning time m 08:50-12:10
> acl mondayafternoon time m 12:20-15:40
> acl mondaynight time m 17:50-21:10

Looks good.

> #MONDAY MORNING
> http_access deny mondaymorning 1022
> http_access deny mondaymorning 1029
> http_access deny mondaymorning 1030
> #http_access deny mondaymorning 1031
> http_access deny mondaymorning 1032
> http_access deny mondaymorning 1033
> http_access deny mondaymorning 1034

How are 1022 & friends defined? You might be able to combine them
into a single ACL defined in a file, as mentioned above. You could
then do something like:

    http_access deny mondaymorning aclname

> #MONDAY AFTERNOON
> http_access deny mondayafternoon 1022
> #http_access deny mondayafternoon 1029
> http_access deny mondayafternoon 1030
> #http_access deny mondayafternoon 1031
> #http_access deny mondayafternoon 1032
> http_access deny mondayafternoon 1033
> #http_access deny mondayafternoon 1034

Likewise.

-- 
Michael Fuhr
http://www.fuhr.net/~mfuhr/
Received on Mon Oct 12 1998 - 00:07:48 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:25 MST