Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 7888 invoked from network); 20 Nov 2003 03:53:45 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Nov 2003 03:53:45 -0000 Received: (qmail 3644 invoked by uid 500); 20 Nov 2003 03:53:20 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 3595 invoked by uid 500); 20 Nov 2003 03:53:20 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 3582 invoked from network); 20 Nov 2003 03:53:20 -0000 Received: from unknown (HELO netspace.org) (64.61.61.206) by daedalus.apache.org with SMTP; 20 Nov 2003 03:53:20 -0000 Received: from netspace.org (localhost.localdomain [127.0.0.1]) by netspace.org (8.12.10/8.12.10) with ESMTP id hAK3qwCu016925 for ; Wed, 19 Nov 2003 22:52:58 -0500 Received: (from gs@localhost) by netspace.org (8.12.10/8.12.10/Submit) id hAK3qwUY016923 for dev@httpd.apache.org; Wed, 19 Nov 2003 22:52:58 -0500 Date: Wed, 19 Nov 2003 22:52:58 -0500 From: Glenn To: dev@httpd.apache.org Subject: accessing userdir mapping info Message-ID: <20031120035258.GA15238@netspace.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N There are numerous modules that provide "userdir" mappings in Apache. mod_userdir (a standard module), mod_ldap_userdir, mod_dynvhost, ... I'm sure there are others. But there is no generic way that I am aware of for other modules to access this information. Apache2 mod_userdir sets "mod_userdir_user" with the username and this note is required by suexec in Apache2. But how well does this work with other userdir-mapping modules? Does this bypass suexec mechanisms? And what about access to the path to the userdir, which might not be the homedir, and in any case other modules have no idea what suffix (e.g. "public_html/") is appended to the homedir. I'd love to see an generic method for other modules to access this information. The quickest would be to have the userdir-mapping modules set notes in r->notes table such as "userdir_user" and "userdir_path". Or would people prefer an optional registered function along the lines of ap_get_userdir_info(request_rec *r, char **user, char **path) that would fill in user and path, or set them to NULL if not a userdir request? I'm not sure which would be more efficient; a notes table lookup of information set by the userdir-mapping module, or calling a function which would require the userdir-mapping module to reparse the URI or (possibly) remake expensive database queries. (In such a case, the userdir-mapping module might just as easily set its own private notes (private in the sense of not intended for use by others) in the r->notes table to avoid having to redo any lookups) I'm happy to make the patches if there is support for this. Thoughts? Cheers, Glenn