DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25460>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25460 <IfDefine >, <IfModule > are valid syntax Summary: <IfDefine >, <IfModule > are valid syntax Product: Apache httpd-2.0 Version: 2.1-HEAD Platform: Other URL: http://marc.theaimsgroup.com/?t=107089936600004&r=1&w=2 OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] this was first posted on httpd-dev http://marc.theaimsgroup.com/?t=107089936600004&r=1&w=2 currently, all core container directives have an issue (albeit a minor one) - they require an argument in practice but are allowed to proceed without one during configuration. for example <IfModule > does not currently throw an error. instead, the config is allowed to proceed, soaking up the container. more details are available within the thread. there has been discussion on httpd-dev whether <IfDefine > should be allowed, equally split between the two people who voiced their opinion. this patch attempts to bridge the gap, requiring that core containers specify arguments, while <IfDefine 0> is guaranteed to never be true (-D0 becomes invalid, similar to -D""), thus providing a migration path away from <IfDefine >. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
