From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 Description of problem: Problem applies to RedHat 9 and Fedora Core 1. httpd ships with /etc/httpd/conf.d/ssl.conf in order to facilitate https setup. However, this default configuration conflicts with use of NameVirtualHost. To use NameVirtualHost one has to rename ssl.conf so that it does not get loaded. There are probably other/better ways to do it, but I am not aware of them. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install RedHat 9/Fedora Core 1 2. Try to set up a NameVirtualHost - and fail 3. delete or rename /etc/httpd/conf.d/ssl.conf - NameVirtualHost works Actual Results: The default configuration should allow use of NameVirtualHost. Additional info: I don't know enough about apache config to make any specific recommendations. But someone who knows about it should be able to make some config changes so that the default config does not break NameVirtualHost. If not, then there should be descriptive text in the /etc/httpd/conf/httpd.conf file which warns about the conflict between NameVirtualHost and ssl
What NameVirtualHost directive did you use which conflicts with ssl.conf? One without ":80" at the end?
Correct ... I never specify :80 because on a couple of machines I listen on other ports.
That is simply a config error. I'll add this to the default httpd.conf for the next release: # # NOTE: NameVirtualHost cannot be used without a port specifier # (e.g. :80) if mod_ssl is being used, due to the nature of the # SSL protocol. #