Received: by taz.hyperreal.com (8.6.12/8.6.5) id FAA21428; Wed, 17 Jan 1996 05:48:36 -0800 Received: from discovery.brad.ac.uk by taz.hyperreal.com (8.6.12/8.6.5) with SMTP id FAA21406; Wed, 17 Jan 1996 05:48:14 -0800 Received: from morph.acc.brad.ac.uk by discovery.brad.ac.uk; Wed, 17 Jan 1996 13:48:02 GMT Received: from osprey.brad.ac.uk (mjhcox@osprey.cen.brad.ac.uk [143.53.238.18]) by morph.acc.brad.ac.uk (8.7.2) with SMTP id NAA03720 for ; Wed, 17 Jan 1996 13:49:44 GMT Date: Wed, 17 Jan 1996 13:46:48 +0000 (GMT) From: Mark J Cox X-Sender: mjhcox@osprey To: new-httpd@apache.org Subject: Some more for the List In-Reply-To: <199601161355.HAA20798@sierra.zyzzyva.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com Four more things for the list... Bugs: Fix timeout code so it resets properly after every sucessful byte I haven't tried out the most recent method that was posted for this Wish List: Restrict/Enable ~user on a per-user basis (separate module probably) So you can easily suspend troublesome users or only allow users that have signed some disclaimer Mutiple Configurable Log Files This would get rid of the need for the agent and referer modules (and cookie logs). You could "AddLog filename [config]" for as many log files as you want. "RefererLog filename" is then just an alias for "AddLog filename $O{referer}" (or whatever syntax). Named Access Methods You could specify a set of restrictions and re-use those restrictions in other areas. I've seen sites have multiple "local only" sections that are fairly complex (allow from this domain but not the proxy server etc.) that are repeated many times throughout the site. Mark Mark J Cox, mark@awe.com -------------- URL:http://www.awe.com/mark.html University of Bradford, England ---------- tel +44.1274.384070/fax 391333