On Tue, 5 Nov 2002 08:48:58 +0100
"Boyle Owen" <[EMAIL PROTECTED]> wrote:
> No. This is called name-based virtual hosting (NBVH). It works fine for
> plain HTTP but is impossible under SSL.
>
> The reason is that NBVH uses the "Host" header to find the VH. But in
> SSL, the connection must be est
Yes indeed, although this is a rather limited case of NBVH.
-Original Message-
From: [EMAIL PROTECTED] [mailto:ueli@;heuer.org]
Sent: Dienstag, 5. November 2002 10:08
To: [EMAIL PROTECTED]
Subject: Re: Configuring Multiple Certicates SSL over an unique IP
On Tue, 5 Nov 2002 08:48:58 +010
I'm thinking you need to use Virtual Host directives - as others have
replied, you already know that NameVirtualHost wont help - so you need
to put each virtual host on a different IP. (or different port if no
spare IP's_).
firstly - configure your operating system to receive all the ip's you
Don't forget:
Listen 192.168.1.2:443
Listen 192.168.1.3:443
-Original Message-
From: Peter Viertel [mailto:peter.viertel@;itaction.co.uk]
Sent: Dienstag, 5. November 2002 14:17
To: [EMAIL PROTECTED]
Subject: Re: Configuring Multiple Certicates SSL over an unique IP
I'm thinking you nee
Hi,
We are working with apache-1.3.23 and mod_ssl-2.8.7,
sometimes explorer says:
"This page contains both secure and nonsecure items. Do you want to display the
nonsecure items?"
While everything on the page is secure, when answering yes, we always get a 'page
cannot be displayed'
The proble
How does one go about getting a star certificate?
> -Original Message-
> From: Boyle Owen [mailto:Owen.Boyle@;swx.com]
> Sent: Tuesday, November 05, 2002 5:22 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Configuring Multiple Certicates SSL over an unique IP
>
>
> Yes indeed, although this
Only Thawte do starred certificates, www.thawte.com, however they are now
fairly restrictive on allowing them. You have to contact a representative
first (ie you can no longer get them online).
We are probably not going to bother renewing our current one because they
are now too much hassle.
-
J
The default:
Listen 443
achieves this already. Is there some advantage to doing separate Listen's?
Boyle Owen wrote:
Don't forget:
Listen 192.168.1.2:443
Listen 192.168.1.3:443
-Original Message-
From: Peter Viertel [mailto:peter.viertel@;itaction.co.uk]
Sent: Dienstag, 5. November
