Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 3087 invoked by uid 6000); 18 Nov 1999 14:26:13 -0000 Received: (qmail 3078 invoked from network); 18 Nov 1999 14:26:11 -0000 Received: from internal.mail.demon.net (193.195.224.3) by taz.hyperreal.org with SMTP; 18 Nov 1999 14:26:11 -0000 Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id OAA19739; Thu, 18 Nov 1999 14:26:09 GMT Received: from fanf by fanf.eng.demon.net with local (Exim 3.03 #2) id 11oSVG-000IdS-00 for new-httpd@apache.org; Thu, 18 Nov 1999 14:25:38 +0000 To: new-httpd@apache.org From: Tony Finch Subject: Re: UseCanonicalName no longer in Directory containers? In-Reply-To: References: Message-Id: Date: Thu, 18 Nov 1999 14:25:38 +0000 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Ryan Bloom wrote: > >> It would be nice if 2.0 had more fine-grained admin control of >> .htaccess files... > >Do I hear a volunteer????? :-) I hesitate to sign up when I don't know where the time would come from, but I've thought about it a little. Would it be acceptable to significantly break compatibility with the 1.3 configuration language? What I would do is throw away the Options directive and replace it with a separate directive to control each option. I would also replace AllowOverride with a more generic system that could {en,dis}able each directive from appearing in .htaccess files, individually or in groups. (I haven't thought much about how to define groups of directives.) Tony. -- dot it at