On 19/03/2013 3:03 a.m., Sébastien WENSKE wrote:
Hey,
It would be great if this feature becomes available !!!
Then please submit a Feature Request bug.
acl aclname_1 type_1
acl aclname_2 type_2
acl aclname_3 type_3
acl aclname_4 type_4
[...]
http_access allow|deny aclname_*
Cheers!
-----Message d'origine-----
De : Nick Cairncross
Hi all,
Just a quick question today..: In a bid to keep to some standards my ACLs
all follow similar naming conventions :
FILETYPE_EXE_[object] - e.g. FILE_TYPE_EXE_Users, FILE_TYPE_EXE_Hosts,
FILE_TYPE_EXE_IPAddresses FILETYPE_MP3_[object] - e.g. FILE_TYPE_MP3_Users,
FILE_TYPE_MP3_Hosts, FILE_TYPE_MP3_IPAddresses FILETYPE_ZIP_[object] - e.g.
FILE_TYPE_ZIP_Users, FILE_TYPE_ZIP_Hosts, FILE_TYPE_ZIP_IPAddresses
Instead of repeating the deny_info entry three times for each of these, is
it possible to use a wildcard for one? If so.. What is it?:
deny_info CUSTOM_FILEBLOCKED FILETYPE_{wildcard}
Have you considred making this a dynamic external_acl_type helper lookup?
The helper can return a message="blah" parameter to be embeded in a
single error page which contains your variable explanation part.
Amos
