Bug 31712

Summary:	config_file is NULL at ap_walk_config etc
Product:	Apache httpd-2	Reporter:	Anton Lavrentiev <lavr>
Component:	Runtime Config	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	enhancement	Keywords:	MassUpdate
Priority:	P3
Version:	2.0.51
Target Milestone:	---
Hardware:	All
OS:	All

Description Anton Lavrentiev 2004-10-14 03:07:45 UTC

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

Comment 1 William A. Rowe Jr. 2018-11-07 21:08:22 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.