On Thu, Jan 8, 2009 at 8:45 AM, Brian Mearns <mearns.b@xxxxxxxxx> wrote: > On Thu, Jan 8, 2009 at 1:28 AM, Krist van Besien > <krist.vanbesien@xxxxxxxxx> wrote: >> On Wed, Jan 7, 2009 at 4:27 PM, Brian Mearns <mearns.b@xxxxxxxxx> wrote: >> >>> Right, which I guess is a big problem for most use cases. For me, my >>> certificate is self-signed anyway, and I already use it for multiple >>> hostnames (myserver.net, www.myserver.net, web.myserver.net, which are >>> all aliased to the same vhost in apache). >> >> Than there is no reason not to have the virtualhosts all on the same >> server... Your solution is unnecessarily complicated. > > Is that possible if I want to serve both secure and unsecure (80 and > 443)? If I just setup my root configuration (i.e., not in a vhost) to > listen on port 80 and 443 and turn on the SSL engine, then all the > content will be encrypted, won't it? No, you can turn on SSL in a single virtualhost (<virtualhost *:443>) and serve non-SSL from either the "base" server or another virtual host (<virtualhost *:80>) -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|