Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id SAA02165; Mon, 25 Aug 1997 18:25:29 -0700 (PDT) Received: from plato.alameda-coe.k12.ca.us (plato.alameda-coe.k12.ca.us [206.110.1.34]) by hyperreal.org (8.8.5/8.8.5) with SMTP id SAA02161 for ; Mon, 25 Aug 1997 18:25:26 -0700 (PDT) Received: from pappilloma.wwebsvs.com by plato.alameda-coe.k12.ca.us with smtp (Smail3.1.29.1 #5) id m0x3ADP-000OezC; Mon, 25 Aug 97 18:14 PDT Received: from ace.nueva.pvt.k12.ca.us by pappilloma.wwebsvs.com (SMI-8.6/SMI-SVR4) id RAA07990; Mon, 25 Aug 1997 17:19:23 -0700 Received: from localhost by ace.nueva.pvt.k12.ca.us with SMTP (1.37.109.24/15.5+ECS 3.3+HPL1.1) id AA254028721; Mon, 25 Aug 1997 18:25:21 -0700 Date: Mon, 25 Aug 1997 18:25:20 -0700 (PDT) From: Alexei Kosut To: new-httpd@apache.org Subject: Re: SymLinksIfGroupMatch In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 25 Aug 1997, Dean Gaudet wrote: > FWIW I just ran into a situation where I would find such an option useful. > I have a docroot which is writable by a group of people, and they just put > in a symlink for which the target is the same group ... and now my server > won't serve the page because I'm only using SymLinksIfOwnerMatch. So I > wouldn't mind adding the group feature ;) On a related issue... I've often thought it would be nice if the Options directive was extensible by modules. Right now, if a module wants to set up a per-dir configuration that involves something like a directory option, they have to create a per-dir config, add in the directive handler, merger, etc... For modules which don't already have directives, this is additional hassle and bloat For example, it has come up that one might want status reports to only be allowed to be sent by the main server conf, so someone couldn't use AddHandler in their .htaccess file to send server status. I think this was solved another way (though I may be wrong), but it seems to me this might be an interesting way of doing it: Allow Options to be given arbitrary text strings, which it stores in an array. It takes care of merging, etc... Then mod_status' handler can just call rcheckoption("Status"), to see if that option has been set in the current directory. If not, it won't send the status report. That way, unless AllowOverrides Options has been enabled, you can't generate status reports unless the server admin explictly adds "Options Status" to the directory. One problem with this is that it would reduce the capacity for Options to do error checking, unless you set up some way of registering Options strings. But I think it's an interesting idea. -- Alexei Kosut