... passes the config parsing with flying colors, even when it's meaningless.

Is there a reason we are allowing unrecognized/unparsed blocks into the config? 
 
I would expect we would want to error out.

I discovered this with my <Proxy proxy:location> patch, when I forgot
to load the proxy module.  We wouldn't accept an unrecognized directive,
why accept an unrecognized block tag?

Bill

Reply via email to