Nope.. It didn't work. We didn't see anything.
-Original Message-
From: Kyle O'Donnell [mailto:[EMAIL PROTECTED]]
Sent: Sonntag, 12. Januar 2003 12:41
To: [EMAIL PROTECTED]
Subject: sorry all, test
test
__
Apache
On Sun, Jan 12, 2003 at 09:23:27PM -0600, Barry Smoke wrote:
o.k...you have my attention now...
wildcard certificate?
Can wildcard certificates be purchased, or is this only if you are self
signing?
According to Thawte's website they still issue wildcard certs.
I sure would like to buy one
I believe you can get wildcard certs from Thwate. Check out their site.
NB - wildcards are like *.acme.com so www1.acme.com, www2.acme.com etc
all work. You cannot get *.*.com to work in any case.
Rgds,
Owen Boyle
-Original Message-
From: Barry Smoke [mailto:[EMAIL PROTECTED]]
Sent:
-Original Message-
From: James Collier [mailto:[EMAIL PROTECTED]]
I realise I am on thin ice as it would be a reasonable
optimisation to assign the final virtual host at an earlier
stage than is currently the case with SSL.
I wouldn't worry too much. Currently, in an SSL transaction,
Sorry - I didn't express that very well, but thanks for the reply.
At the moment, the handshake take place using the first matching vhost
on the basis of IP+Port, but evidently Apache then scans the decrypted
host header and assigns the correct NBVH. This is using 1.3.x; I haven't
tested 2.x
-Original Message-
From: James Collier [mailto:[EMAIL PROTECTED]]
At the moment, the handshake take place using the first matching vhost
on the basis of IP+Port, but evidently Apache then scans the decrypted
host header and assigns the correct NBVH.
Exactly. The SSL transaction is
Boyle Owen [EMAIL PROTECTED] writes:
- IPv6 will take off, creating so many IP addresses that NBVH will be
unnecessary and we will revert to one site, one IP.
There is already a document describing how to do this with SSL/TLS
in the IETF standards pipeline.
-Ekr
--
[Eric Rescorla
On Mon, Jan 13, 2003 at 07:32:24AM -0800, Eric Rescorla wrote:
There is already a document describing how to do this with SSL/TLS
in the IETF standards pipeline.
Unfortunately this is not implemented very many places - so far the only
place I've heard of is Apache 2.1 which has some
Mads Toftum [EMAIL PROTECTED] writes:
On Mon, Jan 13, 2003 at 07:32:24AM -0800, Eric Rescorla wrote:
There is already a document describing how to do this with SSL/TLS
in the IETF standards pipeline.
Unfortunately this is not implemented very many places - so far the only
place I've
I am having trouble getting the SSLSessionCache directive
working on Win NT and have been unable to find any examples
or information where others have been able to implement this.
Does anyone know if this directive is supported on Win32?
Many thanks Owen - I'll sleep more easily now ;)
Boyle Owen wrote:
-Original Message-
From: James Collier [mailto:[EMAIL PROTECTED]]
At the moment, the handshake take place using the first matching vhost
on the basis of IP+Port, but evidently Apache then scans the decrypted
host
...depends on your configuration. SSLSessionCache works fine with my apache
1.3.27, but I had some problems with apache 2. with 2.0.39, session cache
was not honoured on win32 (bugzilla 10170), but this may have changed in the
meantime.
rgds
michael
-Ursprüngliche Nachricht-
Von:
Are there any docs for setting this up?
thanks
Robert
- Original Message -
From: James Collier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 13, 2003 12:29 PM
Subject: Re: Confession: I use NBVHs with SSL (was Re: 2 VirtualHosts with 2
Certificates)
Many
13 matches
Mail list logo
