Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id LAA19537; Mon, 11 Aug 1997 11:23:57 -0700 (PDT) Received: from valis.worldgate.com (marcs@valis.worldgate.com [198.161.84.2]) by hyperreal.org (8.8.5/8.8.5) with ESMTP id LAA19525 for ; Mon, 11 Aug 1997 11:23:51 -0700 (PDT) Received: from localhost (marcs@localhost) by valis.worldgate.com (8.8.5/8.8.5) with SMTP id MAA13638 for ; Mon, 11 Aug 1997 12:23:44 -0600 (MDT) Date: Mon, 11 Aug 1997 12:23:44 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: Re: BindAddress In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Guck. So what you are saying is that to have a web server that listens on two ports work properly you need to have a VirtualHost section for one with a different Port statement? Guck. Is this a feature? On Mon, 11 Aug 1997, Alexei Kosut wrote: > On Mon, 11 Aug 1997, Paul Sutton wrote: > > > Is there any reason why Port is needed if Listen is being used? > > Yes. If there are Listen directives, Port is ignored in terms of actually > accepting the connection, but it is used to configure the server. In > other words, if I have the following: > > Listen 5000 > Port 6000 > > Apache will accept connections on port 5000 only, not 6000. However, if I > get a redirect, it will be to "http://servername:6000". > > So replacing the Port in the configuration with a Listen would mean that > anyone who changed the "Listen 80" to any other port would still get > redirects to port 80, which isn't where their server is running anymore. > > -- Alexei Kosut >