Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Errors-To: <admin@rowe-clan.net>
Message-ID: <03bf01c0dfeb$c379ec70$94c0b0d0@roweclan.net>
Reply-To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
From: "William A. Rowe, Jr." <admin@rowe-clan.net>
To: <new-httpd@apache.org>
References: <20010503161142.C12911@viper.eng.sun.com>
Subject: Re: [PATCH] option to remove default listener
Date: Fri, 18 May 2001 17:42:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

+1 on this patch, reason being...

we have a bunch of confusion over the port/listen directives.  I believe this
patch is headed in the right direction.

We NEED to depreciate the old Port behavior.  It is terribly confusing to folks
to change their port, and have nothing happen.

Listening should be through a Listen directive, alone.  A few folks need to
change the .conf file, but this is 2.0, so everyone will be changing their
.conf file for varied reasons.

By assuming port 80, we make the user believe that the Port directive is actually
in control of something.  Of course, it's not.

Let's get the pain over with, finally.  If they forget Listen, then don't make
assumptions for them.

Bill


----- Original Message ----- 
From: "Danek Duvall" <dduvall@eng.sun.com>
To: <new-httpd@apache.org>
Sent: Thursday, May 03, 2001 6:11 PM
Subject: [PATCH] option to remove default listener


> When we packaged up Apache for delivery with Solaris, we had a requirement
> that it not be run by default at boot-time unless it was explicitly
> configured by an administrator.  We did this by moving the configuration
> file out of place, and putting a few lines in the boot script to check for
> the placement of the config file.
> 
> The reason for all this rigmarole was so that if a customer upgraded a
> system without Apache to a version of the OS which came with Apache, then
> it wouldn't clobber any other web server they might happen to have
> installed and configured.
> 
> We are considering using Apache to host an IPP server, and this kludge no
> longer works the way we'd like.  Essentially, we need a solution whereby
> Apache will not listen on port 80 unless it is explicitly configured to do
> so.  Since currently it will create a server on port 80 if nothing else is
> configured, we need for this behavior to change.
> 
> I'm attaching a patch which disables this creation of a default listener by
> passing httpd a new config define -- NO_DEFAULT_LISTENER.  With the patch,
> unless someone has specified a Port or Listen directive (or otherwise added
> a listener), apache will read its configuration files and keel over.
> 
> Please consider this for inclusion into Apache 2.0.
> 
> Thanks,
> Danek
>