Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 19780 invoked by uid 500); 14 Nov 2001 16:50:01 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 19761 invoked by uid 501); 14 Nov 2001 16:50:00 -0000 Date: 14 Nov 2001 16:50:00 -0000 Message-ID: <20011114165000.19760.qmail@apache.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org, From: "Andrew Gilmartin" Subject: Re: mod_autoindex/8745 Reply-To: "Andrew Gilmartin" The following reply was made to PR mod_autoindex/8745; it has been noted by GNATS. From: "Andrew Gilmartin" To: Cc: Subject: Re: mod_autoindex/8745 Date: Wed, 14 Nov 2001 11:39:49 -0500 The problem is not with mod_autoindex, but with mod_dir's handling of the internal redirect. Mod_dir knows nothing about the files listed in DirectoryIndex: It just tries to do an internal redirect to each file listed until one succeeds. The internal redirect looks different than mod_include's, for example, in that mod_include knows when it is calling a CGI script and so sets the redirect's environment by calling ap_add_common_vars(r); ap_add_cgi_vars(r); Mod_dir's does not have this foreknowledge and so (ultimately) only calls ap_add_common_vars(r); which does not setup PATH_INFO, etc. From what I can tell from reading the code so far is that mod_dir needs a special internal redirect is more aware of the parent environment. That is the directory's uri is the path info to the script at the given directory index. --- Andrew Gilmartin Senior Developer Ingenta andrew.gilmartin@ingenta.com andrewgilmartin (aim) 401-743-3713 (cell)