The argument that this is a reversion to the httpd/access/srm
	multifile scenario is bogus, IMHO; the problem with those
	was that their purposes were not clear, nor were the orders
	of invocation.  Putting massive (or tiny but uncommon) chunks
	of easily self-contained special-function directives into
	separate files simplifies the basic configuration and doesn't
	revert to either of the trinity-file complaints, since these
	would need to be explicitly invoked with an Include directive.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91524 13f79535-47bb-0310-9956-ffa450edef68