DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31712>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31712 config_file is NULL at ap_walk_config etc Summary: config_file is NULL at ap_walk_config etc Product: Apache httpd-2.0 Version: 2.0.51 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Runtime Config AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Hi, There are few things to improve, if you don't mind: 1. server/config.c:execute_now() should not check for command existence in modules as it has been just [successfully] done before, in ap_build_config_sub(), the sole caller of execute_now(). 2. cmd_parm::config_file is NULL when command handlers (command_rec*) are invoked [via invoke_cmd()], for "normal" commands (cf ap_walk_config[_sub]()). This limitation is in discrepancy with Apache 1.3 API, yet ap_directive_t commentary notices that file and line_num fields would be gone in the future. If so, then how it would be possible to report an error to the user using file:line coordinates from the command handler. The field cmd_parm::config_file is now okay (!=NULL) only for EXEC_ON_READ commands, but then "mconfig" [middle] argument for the command handler is passed NOT as a module config, but as a configuration subtree :-( This kind of hacks makes development of extensions very difficult. Thanks for considering this. Anton Lavrentiev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
