>Number: 2059 >Category: config >Synopsis: Previous versions of APACHE (I had been using 1.3b1) allow the >same IP for a virtual host, when I switched to 1.3b5, it did not allow it. I >could not find 1.3b1, so I tried 1.2.5 and 1.3b3, and neither worked. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: support >Submitter-Id: apache >Arrival-Date: Sun Apr 12 18:10:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.5, 1.3b1 1.3b3 1.3b5 >Environment: FreeBSD engulf.com 3.0-CURRENT >Description: MEMBERS.ENGULF.COM was using *.MEMBERS.ENGULF.COM in the NS to point to this IP (207.96.124.102), in the adduser script, I had it echo a virtual host into the httpd.conf, so the same IP had about 50 users. <UserName.Members.EngulF.Com> would go to /usr/home/homedir/www. Then, when I upgraded to 1.3b5, assuming it would stay the same, it would not allow this. The virtual host should check the hostname that the client is trying to connect to, not the IP. >How-To-Repeat:
>Fix: As above, 1.3b1 apparently checked the hostname the client was checking for, not the IP. Maybe that should be put back the old way >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
