httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@covalent.net>
Subject Re: [PATCH] Remove the Port directive.
Date Thu, 04 Oct 2001 13:13:18 GMT
From: "Rodent of Unusual Size" <Ken.Coar@Golux.Com>
Sent: Thursday, October 04, 2001 6:26 AM


> Ryan Bloom wrote:
> > 
> > This patch completely deprectates the Port directive.
> > The ServerName directive is now overloaded, so that
> > admins specify the port and name on the same directive.
> > It also makes Listen a required directive.
> 
> I must have missed something.  Just WTH is the motivation
> for all this?  I foresee nasty interactions with
> <VirtualHost>, among other things.

A four month long conversation on list between just about
everybody, that the BindAddress duplicated Listen, and the
Port directive was too broken for most users to understand.

Now our users have exactly _two_ directives to comprehend:

Listen controls what addresses and ports the server listens on;

Listen 80   [Listen to port 80 on all IP addresses bound to this machine]
Listen 10.0.0.10:80  [Listen to just the 10.0.0.10 IP address, port 80]

ServerName defines the server's OWN name for itself, including 
it's port if it is a nonstandard assignment;

ServerName this.host.com       [assumes the default port 80]
ServerName this.host.com:8080  [specified this server runs on port 8080]

And if you are correct, that this breaks VirtualHost, then we have a
bug and we better fix that before Ryan's commit.  But this makes the
server easier to understand.  Just WTF is a Port directive that doesn't
actually choose a port?  Since Listen overrides the Port directive, I
spend most of my time on newslists asking the user for _every_ bindaddr,
listen, port and servername, which is overkill.

Bill


Mime
View raw message