On 21 Mar 2010, at 10:14 PM, William A. Rowe Jr. wrote:
The gist of my objection is this illegitimate behavior;
Include conf/extra/*.duh
Include conf/extra/*/doh.conf
Include conf/empty/*
Include conf/*/whoops.conf
The last one (based on an existing conf/empty directive) fails,
alerting the admin
to the fact that they made a typo, which is good.
The others all fail-to-fail with this logic [based on the absence of
any matching
directories in the extra/ folder]. That's unacceptable.
I've just been trying to pick apart the original behaviour (pre
patch), and as Dan has pointed out, this patch makes no change to the
existing behaviour of v2.2 or trunk: options 1 and 3 both succeed in
httpd v2.2.13 and v2.2.14 (which you are attempting to veto), and
options 2 and 4 fail as wildcards are not supported (as expected).
As a result, the change you want cannot be backported to v2.2 as it
will break existing configurations, and the veto is therefore invalid.
I suspect it has worked like this in the past, I have no idea when
this behaviour was changed.
Regards,
Graham
--
