question about include directives

[Andrew Boyce-Lewis <ab...@conduit-it.com>]

I am wondering why the include directive does not allow wildcard
constructions in the directory path. For example, 'include
/etc/httpd/*/*.conf' will not work and will produce the error "wildcard
patterns not allowed in Include"

However 'include /etc/httpd/dir/*.conf' works as expected. 

I tested all of this with apache 1.3.31. 

This seems like an unnecessary limitation. 

Any insight?

 -Andrew
-- 
Andrew E. Boyce-Lewis
Conduit-IT
Phone: 	800 493-5045 x 210
Fax:	(814) 867-8248
Cell:   (814) 360-6868
GPG key available at http://dev.conduit-it.com/~aboyce/aboyce.gpg

Re: question about include directives

[André Malo <nd...@perlig.de>]

* Andrew Boyce-Lewis <ab...@conduit-it.com> wrote:

> 
> I am wondering why the include directive does not allow wildcard
> constructions in the directory path. For example, 'include
> /etc/httpd/*/*.conf' will not work and will produce the error "wildcard
> patterns not allowed in Include"
> 
> However 'include /etc/httpd/dir/*.conf' works as expected. 
> 
> I tested all of this with apache 1.3.31. 
> 
> This seems like an unnecessary limitation. 

It's *way* more effort to resolve arbitrary path wildcards as well and
there's much recursion involved. So it's not really unnecessary, but just
lazy.

Patches welcome :-)

nd