On 11/8/05, Boyle Owen [EMAIL PROTECTED] wrote:
The point about Apache 2.1 is that it includes a new module (as mentioned by
Nick) which supports a new extension to TLS. This allows for Server Name
Indication where the client tells the server what hostname it wants to
connect to. Basically,
Boyle Owen wrote:
BTW, I didn't write the line below so don't attribute it to me...
mod_ssl Added a support for RFC 2817, which allows
connections to upgrade from clear text to TLS encryption.
No, that would be from the Apache 2.1 Changelog. I was also pessimistic
when I saw the
-Original Message-
From: John P. Speno [mailto:[EMAIL PROTECTED]
Sent: Sonntag, 6. November 2005 00:07
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Limiting SSL to a specific virtual host
On a 1.3.27 server with 1 IP address and 3 name based virtual hosts.
As it is
Folks, ALL flavors of mod_ssl can do name based hosting, but it's entirely
irrelevant unless you use a wildcard certificate who's pattern matches all
of the domains hosted. Because the server and client handshake a specific
set of certificates LONG BEFORE the client ever sends the 'Host:
On 11/7/05, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
The biggest problem is that you can't identify connection upgrade in the
scheme name - so there's no good user interface to help the user request SSL
upgrade where available and when desireable, and there's not a really good
way to
On Monday 07 November 2005 12:31, Nick Kew wrote:
On Monday 07 November 2005 12:13, Olaf van der Spek wrote:
On 11/7/05, Boyle Owen [EMAIL PROTECTED] wrote:
NB - Remember that you can't do name-based VHs with SSL.
I think Apache 2.1 can.
You're thinking of mod_gnutls, which IIRC works
-Original Message-
From: Joost de Heer [mailto:[EMAIL PROTECTED]
Sent: Montag, 7. November 2005 19:12
To: Boyle Owen
Cc: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Limiting SSL to a specific virtual host
NB - Remember that you can't do name-based VHs with SSL.
I