|Summary:||old-style <directory proxy:*> doesn't give any warnings|
|Product:||Apache httpd-2||Reporter:||Joachim Wagner <jwagner>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description Joachim Wagner 2006-04-29 14:51:31 UTC
When copying from old 1.3 configurations there is no warning that <Directory proxy:*> Order allow,deny Allow from localhost </Directory> doesn't protect the proxy server. As far as I understand the directory directive in 2.0, the first argument must either be "~" or start with '/'. Enforcing this should be sufficient to motivate users to have another look at the documentation and spot that <proxy *> must now be used. As this feature request is security related, I chose severity 'minor' instead of 'trivial'.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:00 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.