["William A. Rowe, Jr." <wr...@rowe-clan.net>]

... 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

Re:

[Jeff Trawick <tr...@attglobal.net>]

"William A. Rowe, Jr." <wr...@rowe-clan.net> writes:

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

maybe the issue is location-dependent?  I just added

<Someunknown block>
</Someunknown>

to the very top of my file and get

[trawick@rdu88-250-106 httpd-2.0]$ ./httpd -t
Syntax error on line 1 of /home/trawick/apacheinst/conf/httpd.conf:
Invalid command '<Someunknown', perhaps mis-spelled or defined by a module not included in the server configuration

> Is there a reason we are allowing unrecognized/unparsed blocks into the config?  

bug

> I would expect we would want to error out.

yes


-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...

Re:

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

----- Original Message ----- 
From: "William A. Rowe, Jr." <wr...@rowe-clan.net>
To: <de...@apr.apache.org>
Sent: Saturday, August 25, 2001 10:01 PM
Subject: <Someunknown block>


> ... 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
> 
>