"William A. Rowe, Jr." wrote: > > Now our users have exactly _two_ directives to comprehend: > > Listen controls what addresses and ports the server listens on; > > ServerName defines the server's OWN name for itself, including > it's port if it is a nonstandard assignment;
All right, got it. > And if you are correct, that this breaks VirtualHost, then > we have a bug and we better fix that before Ryan's commit. I am not sure if it breaks it or not, but having lots of flexibility for specifying name/address/port in the <VirtualHost> open directive bungs up the cleanliness. Listen 80 ServerName Foo.Com <VirtualHost OtherFoo.Com:8080> What happens? Presumably the vhost will never hear anything, but will/should we detect it and report it? Also, from your example: > ServerName this.host.com [assumes the default port 80] except that Ryan said there is no default port any more. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "All right everyone! Step away from the glowing hamburger!"
