httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25077] New: - <virtualhost> directive awkward
Date Fri, 28 Nov 2003 23:40:41 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25077>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25077

<virtualhost> directive awkward

           Summary: <virtualhost> directive awkward
           Product: Apache httpd-2.0
           Version: 2.0.47
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_vhost_alias
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: marc@perkel.com


I'm running about 75 virtual hosts and I just upgraded to version 2.0.47 and the
<VirtualHost> directive is both incompatible and awkward to use in 2.0.

Specifically, I have to specify a port number for every virtual host as well as
the namedvirtualhost directive. I did get it to work - but it wasn't pretty and
it was somewhat disapointing. With 1.3 I didn't have to specify the port.

If I specify no port it assumes port 0 - a bzzare assumption.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message