|Summary:||DocumentRoot check incorrect when running under chroot|
|Product:||Apache httpd-2||Reporter:||Philip Pickett <phil.pickett>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description Philip Pickett 2011-08-05 17:47:31 UTC
When running Apache and setting a ChrootDir, the DocumentRoot directory is checked prior to setting up the chroot jail. What this means is that: 1) The main non-chrooted DocumentRoot is checked during started resulting in the "DocumentRoot must be a directory" error being logged and startup failing unless this unused directory exists. 2) There is no check performed for the DocumentRoot in the chroot jail during startup.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:24 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.