Re: config/1817: Compatibility from from 1.2.X to 1.3 with (fwd)

[Dean Gaudet <dg...@arctic.org>]

I would like to change the behaviour of <Files> ... to fix a problem
introduced in 1.3.  I'd like <Files> to apply to *basenames* only.
It makes little sense to me that you can make it apply to full paths,
because we can already get that functionality with:

<Directory /path/prefix>
<Files foo.bar>
...
</Files>
</Directory>

So it seems redundant to try to support:

<Files /path/prefix/foo.bar>
...
</Files>

And things like:

<Files a*b>
...
</Files>

don't work at all in 1.2, which I'm sure is confusing to folks.
This doesn't work because there's no leading wildcard to match the
leading path.

Dean

---------- Forwarded message ----------
Date: 17 Feb 1998 19:51:16 -0000
To: apache-bugdb@apache.org, bartley@purdue.edu, dgaudet@apache.org
From: dgaudet@hyperreal.org
Subject: Re: config/1817: Compatibility from from 1.2.X to 1.3 with <Files>

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]


Synopsis: Compatibility from from 1.2.X to 1.3 with <Files>

State-Changed-From-To: closed-analyzed
State-Changed-By: dgaudet
State-Changed-When: Tue Feb 17 11:51:15 PST 1998
State-Changed-Why:
Ken he's saying that <Files> doesn't behave the same way between
1.2 and 1.3, and he's right.  In 1.3 the wildcard patterns
were changed so that they follow sh-like rules and * doesn't
match /.  Unfortunately <Files> has always matched against the
full pathname.  I believe that is what we should change --
<Files> should match the basename only.  Then we document this
change in the upgrading document.

Dean
Class-Changed-From-To: mistaken-sw-bug
Class-Changed-By: dgaudet
Class-Changed-When: Tue Feb 17 11:51:15 PST 1998