https://bz.apache.org/bugzilla/show_bug.cgi?id=52505
--- Comment #1 from Justin Robinson <[email protected]> --- (In reply to Stefan Fritsch from comment #0) > If you have conf/dirA/foo.conf and conf/dirB (without a conf file in it) the > configuration > > Include conf/*/foo.conf > > gives an error, despite the wildcard expression matching at least one file. > This is a bug. > > > httpd-dev thread starts at > https://slope3.com > http://mail-archives.apache.org/mod_mbox/httpd-dev/201201.mbox/ > %3C201201221914.29589.sf%40sfritsch.de%3E The issue you're encountering with the configuration directive Include conf/*/foo.conf is indeed a recognized bug. The directive is supposed to include all foo.conf files from subdirectories under conf, but if one of those subdirectories (like conf/dirB) does not contain a foo.conf file, it can lead to an error. This behavior suggests that the inclusion process is not handling the absence of matching files gracefully, resulting in an error even when at least one valid file exists. For further discussion or to track the resolution of this bug, you can refer to the relevant thread on the Apache HTTP Server developer mailing list, which starts here. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
