DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34148>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34148 Summary: "Listen" directive is too fascist Product: Apache httpd-2.0 Version: 2.0.53 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] The "Listen" directive, if used with an IP addres, like this: Listen 63.112.169.1:80 will prevent Apache from starting up if that IP address is not bound to any interface. IMHO, as long as there is at least one IP address on which Apache *can* listen, it should complain 'IP address X does not exist, not listening' but otherwise start normally. This behaviour is shown for the 'Virtualhost' directive. If you declare a Virtualhost bound to IP address X but X is not bound to any interface of your machine, this is *not* an error. Why would anyone need this? I have a range of machines and websites. Each website has its own IP address, separate from the machine's IP address. What I want to do is be able to move a website from machine to machine without *any* editing of httpd.conf. In the ideal case, I would say in httpd.conf: Listen <IP-website1>:80 Listen <IP-website2>:80 Listen <IP-website3>:80 Then, on machine 1, I assign <IP-website1> and <IP-website3> to the NIC, restart Apache, and we are rolling. On machine 2, I assign <IP-website2> to the NIC, restart Apache, and all the websites are up. Good idea or what? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
