Sriram Natarajan wrote: > > Seema Alevoor wrote: >>> - Should the file not be simply called 'ssl.conf' >>> >> Can be changed. >> >> >>> instead of 'httpd-ssl.conf' >>> >> Named "httpd-ssl.conf" just to be consistent with the Apache conf naming >> convention. >> > All the files within conf.d need to have the file naming convention > hence requesting for ssl.conf >>
Fine. Will change it to ssl.conf >>> >> But I think it is common to define ServerName inside a VirtualHost. Why >> should it be commented ? >> >> > I am not sure, what do you mean by 'common'. Since, we don't know what By 'common' I mean "widely used". > the actual host name is going to be at the customer end, this could be > simply commented out and customer can enable it. Please note > 'ServerName' is not a required value. It is not a required value but a recommended one. Apache doc says "For optimal reliability and predictability, you should specify an explicit hostname and port using the ServerName directive.For optimal reliability and predictability, you *should* specify an explicit hostname and port using the ServerName directive." > Setting 'ServerName' to loop back IP address is definitely not the right > thing to do. Again, localhost or 127.0.0.1 for ServerName, is also widely used. -- Seema.
