Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 60762] Enhancement: Add support for runtime SNI changes in
 tomcat-embed
Date: Wed, 22 Feb 2017 17:47:34 +0000
Message-ID: <bug-60762-78-BfGvBX0u8O@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-60762-78@https.bz.apache.org/bugzilla/>
References: <bug-60762-78@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
archived-at: Wed, 22 Feb 2017 17:47:44 -0000

https://bz.apache.org/bugzilla/show_bug.cgi?id=3D60762

--- Comment #2 from Jesse <jesse@dreamtsoft.com> ---
In version 8.5.9 that we are running it looks like that method calls
putIfAbsent against the sslHostConfigs map, throwing an
IllegalArgumentException if there is a duplicate SSLHostConfig object for t=
he
given key/hostname.  From what I can tell there is no existing public metho=
d in
8.5.9 to modify an existing SSLHostConfig once loaded, additionally the met=
hods
to do so properly with regard to ssl context release/create are protected.=
=20
Please correct me if my understanding of this is wrong.

Also, in the case where an SSL certificate or SSLHostConfig object needs to=
 be
removed for any reason, this method would not suffice with either behavior.

When you say that the new SSLHostConfig has no effect without bouncing the
whole connector, is this in a newer tomcat version?  Or do you refer to the
newly created SSLHostConfig object that we are creating and putting in the
sslHostConfigs map?  In the latter case we definitely are seeing the newly
created SSLHostConfig object taking effect and new requests to it's hostname
are being served the corresponding certificate.

--=20
You are receiving this mail because:
You are the assignee for the bug.=

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org