>Number: 1829 >Category: mod_autoindex >Synopsis: <Location> and regexes have changed the meaning of >cmd_parms.path >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Feb 18 00:40:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2, 1.3 >Environment: n/a >Description: It used to be the case that cmd->path was the /directory/prefix/ of the enclosing <Directory> or .htaccess when invoking command handlers in modules. mod_autoindex naively assumes that this is still the case. It isn't any longer because regexes, <Location>, and <Files> will set cmd->path to something which is definately not a path.
There is a lot of cruft that can be removed from mod_autoindex -- it does all this full path comparison using the apply_path element in its dir config. All of this is bogus... not only because the meaning of cmd->path has changed, but also because the per_dir nesting takes care of all of it. Dean >How-To-Repeat: >Fix: Get rid of apply_path. Make sure the merging function does the right thing >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
