Bug 52532 - VirtualHost added TWICE to name-virtual-host list when multiple names resolve to same IP address.
Summary: VirtualHost added TWICE to name-virtual-host list when multiple names resolve...
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.21
Hardware: All All
: P4 trivial (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2012-01-26 00:02 UTC by D. Stussy
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description D. Stussy 2012-01-26 00:02:32 UTC
Example:

<VirtualHost www.example.com:80 www.example.org:80>
    ServerName  www.example.com
    ServerAlias www.example.org
...
These two hostnames share an IP address.


When more than one hostname resolves to a given address, the virtual host section is added to that address' name-virtual-host chain more than once.
Result:

192.0.2.1:80       is a NameVirtualHost
         default server ... 
         port 80 namevhost www.example.com (.../httpd.conf:line-X)
         port 80 namevhost www.example.com (.../httpd.conf:line-X)

This problem does not affect the end-result operation of named virtual host resolution.  However, having the same entry appear more than once in a given NVH chain does cause unnecessary and duplicate comparisons (when the NVH isn't matched via its ServerName, ServerAlias, or ServerPath values).

Solution:  One should check the existing NVH chain to see if the entry being added is already on that list before adding it.  I have not even looked at the code so I leave that for someone else more familiar with apache to deal with.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:47 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.