Re: Built-In Apache & HTTPS

> The interesting part of your httpd.conf is missing.

I had one NameVirtualHost line:

NameVirtualHost 209.190.205.236

I tried changing this to "NameVirtualHost 209.190.205.236:80", and then adding "NameVirtualHost 209.190.205.236:443", and neither did the trick. I'm wondering, of course, if this is because I left my <VirtualHost 209.190.205.236> directives alone instead of changing them to <NameVirtualHost 209.190.205.236> (though trying that before changing my NameVirtualHost directives above caused a syntax error).

> No. But you should have a entry like this:

Had that one.

>

>> 2. I have a  directive, though it's got 
>> "SSLEngine on" enabled and it has the same server key/certificate. Should I 
>> comment this out? 

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

Appears to have made no difference.

John Kerbawy suggested that I get a clean httpd.conf and merge my changes into it. If I do so, for all of my <VirtualHost ...> directives, should I leave them as they were, or change them to <NameVirtualHost ...>? Also, would I have to specify "SSLEngine on" for each Virtual Host?

Thanks,
Alex Kirk

[demime 0.98d removed an attachment of type application/pgp-signature] Received on Fri Jan 3 16:01:52 2003