When doing this please keep in mind there is a huge amount of users out
there who are not developers and who will struggle with something like
> <LocationMatch ^/foo/(?<bar>[^/]+)>
> Alias /var/lib/%{env:MATCH_BAR}/baz
> …stuff...
> </LocationMatch>
As long as they are reusing the same code under the hood, I don't think
there is anything wrong with having redundant directives whose only purpose
is to have easier-to-read configurations.
On Sun, Jan 26, 2014 at 11:19 PM, Reindl Harald <h.rei...@thelounge.net>wrote:
>
> Am 26.01.2014 23:11, schrieb Graham Leggett:
> > A look at mod_alias shows it has 7 directives:
> >
> > • Alias
> > • AliasMatch
> > • Redirect
> > • RedirectMatch
> > • RedirectPermanent
> > • RedirectTemp
> > • ScriptAlias
> > • ScriptAliasMatch
> >
> > In theory we only need these three:
> >
> > • Alias
> > • Redirect
> > • ScriptAlias
>
> in real world you would break existing configs like
>
> RedirectMatch 404 ^/.*setup/(.*)$
>
> without handle the non-Match directives also like expressions
> which changes behavior you can't remove Match
>
> however, admins will not appreciate such incompatible changes for no
> *real* good reason, even not in case of major upgrades
>
>
>
