Bug 46442 - Semicolon in allow/deny all rules cause reverse lookups
Summary: Semicolon in allow/deny all rules cause reverse lookups
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_access (show other bugs)
Version: 2.0.53
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2008-12-29 15:20 UTC by David Wilde
Modified: 2018-11-07 21:09 UTC (History)
0 users

httpd.conf file to cause reverse dns lookups (532 bytes, application/octet-stream)
2008-12-29 15:20 UTC, David Wilde

Note You need to log in before you can comment on or make changes to this bug.
Description David Wilde 2008-12-29 15:20:32 UTC
Created attachment 23058 [details]
httpd.conf file to cause reverse dns lookups

A trailing semicolon in an allow all or deny all rule causes a reverse DNS lookup.  Since semicolons, per rfc-952, are used to denote comments in the DNS I think httpd should throw an error condition if it encounters a semicolon in a location where it expects a hostname.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:03 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.