I run a multi-config installation of the apache-2.2.4 in one place, meaning: For our installation I build several httpds with different settings for the suexec-wrapper and place them in one base directory. The first installation is a very complex one involving php as fast-cgi and other special features. This installation is a complete one, using "configure", "make", "make install" and it is put into the following base directory: /sw/rs_aix52/httpd-2.2.4 . For the second installation I also use the typical "configure" and "make" after removing the old build-files with "make clean" and "rm config.cache". Except from the suexec-parameters and the name of the httpd-binary the configure-command is the same as the first one. The installation step of the second run only consists of installing the httpd-binary the suexec-binary and the mod_suexec-module under the base directory: /sw/rs_aix52/httpd-2.2.4 (in sbin and libexec). A third installation is done similar to the second one, giving other suexec-parameters. Running the new installation and calling the server-info page on the second httpd I was totally confused as the output said that the suexec-wrapper run for the second installation is similar to the suexec-wrapper for the first installation I built. After several compile sessions I took a look at the mod_suexec source-directory. Grepping for the suexec-binary I found out that the mod_info-output for the suexec-parameters is hard-coded during build-time. The httpd -V output of the second httpd is correct - it shows the right suexec-bin. So I presume the second httpd uses the right (wanted) suexec-wrapper, but the hard-coded output of the mod_info-module is wrong. Please, can you acknowledge my presumption... And as an enhancement, would it be possible to use the "live" httpd -V output for the suexec-parameters to avoid confusion? Regards Christian
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.