On Thursday 04 October 2001 09:18 am, William A. Rowe, Jr. wrote: > From: "Aaron Bannert" <[EMAIL PROTECTED]> > Sent: Thursday, October 04, 2001 11:04 AM > > > On Thu, Oct 04, 2001 at 11:50:27AM -0400, Rodent of Unusual Size wrote: > > > > ServerName this.host.com [assumes the default port 80] > > > > > > except that Ryan said there is no default port any more. > > > > There is no default Listener anymore, but if you omit the port from > > the ServerName directive, it will default to port 80. > > There isn't anything that says we can't substitute > > Listen 0.0.0.0:80 > > in the absense of _any_ Listen directives. This might be more intuitive.
We could do this, but I am afraid it might lead to the same situation we are in now. Namely, users saying: I just added Listen 443 to my config file, and now it stops listening to port 80. This isn't the only required directive we have, so I don't think it hurts to not have a default, and just require a Listen directive. > Speaking of which, would it be good to make a seperate proxy.conf and > (within subprojects) pop.conf, mbox.conf etc? I mention it because proxy, > in particular, adds alot of information to the httpd.conf that some users > never need to review. It seems like it would 'lighten the load'. Of > course, the same logic as ssl; > > <IfModule mod_proxy.c> > Include proxy.conf > </IfModule> > > would be standard in httpd.conf, just as we suggest for ssl. ++1. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
