Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <DDBBD1E00935D144AB9563D57EF98D622F7EBA@raccoon.melandra.net>
References: <DDBBD1E00935D144AB9563D57EF98D622F7EBA@raccoon.melandra.net>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <FCA507B3-05E2-48B8-97F3-B1C05D5C1995@2sheds.de>
Content-Transfer-Encoding: quoted-printable
From: Andrew Miehs <andrew@2sheds.de>
Subject: Re: multiple virtual hosts and ssl certificates
Date: Fri, 25 Aug 2006 15:04:16 +0200
To: "Tomcat Users List" <users@tomcat.apache.org>


Peter is correct - I was just being a bit lazy in my answer...

The ssl connection is setup BEFORE any 'hostname' information is =20
passed over the link, and therefore the server would not know 'which' =20=

virtual hostname's ssl certificate to use.

Therefore - 1 certificate per IP Address/ Port combination.


Cheers

Andrew

On 25/08/2006, at 12:22 PM, Peter Crowther wrote:

>> From: Andr=E9s Gonz=E1lez [mailto:angoro@gmail.com]
>> I mean, what are you saying? That tomcat can only have 1 ssl
>> certificate per IP address, or that it is a "general" limitation of
>> the architecture of SSL certificates.
>
> It is a general limitation of SSL.  To be strict: you can only have =20=

> one certificate per *endpoint*, that is, IP address/port combination.
>

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org