Received: (qmail 13678 invoked by uid 2012); 18 Feb 1998 08:30:58 -0000
Message-Id: <19980218083058.13675.qmail@hyperreal.org>
Date: 18 Feb 1998 08:30:58 -0000
From: Dean Gaudet <dgaudet@arctic.org>
Reply-To: dgaudet@arctic.org
To: apbugs@hyperreal.org
Subject: <Location> and regexes have changed the meaning of cmd_parms.path
X-Send-Pr-Version: 3.2

>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:          feedback
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Feb 18 00:40:00 PST 1998
>Closed-Date:
>Last-Modified:  Tue Aug 07 07:12:58 PDT 2001
>Originator:     dgaudet@arctic.org
>Release:        1.2, 1.3
>Organization:
>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
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-feedback
State-Changed-By: wrowe
State-Changed-When: Tue Aug  7 07:12:58 PDT 2001
State-Changed-Why:
[This is a standard response.]
This Apache problem report has not been updated recently.
Please reply to this message if you have any additional
information about this issue, or if you have answers to
any questions that have been posed to you.  If there are
no outstanding questions, please consider this a request
to try to reproduce the problem with the latest software
release, if one has been made since last contact.  If we
don't hear from you, this report will be closed.
If you have information to add, BE SURE to reply to this
message and include the apbugs@Apache.Org address so it
will be attached to the problem report!
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]