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 > > >> - Instead of line like >> >> #ServerName 127.0.0.1:443 in 'httpd-ssl.conf' , >> >> , it is better to simply comment it so that it looks like >> >> <VirtualHost _default:443> >> #ServerName >> </VirtualHost> >> >> >> This would allow customers to not edit the ServerName field in multiple >> places >> > > 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 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. Setting 'ServerName' to loop back IP address is definitely not the right thing to do.
Thanks Sriram
