-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Diarmuid,
On 9/7/15 12:29 PM, dmccrthy wrote:
> You were right. The issue was with the code our vendor supplied for
> the Tomcat client webapp making outbound HTTPS connections. This
> was not correctly overriding classes with the result that the
>
Hi Chris,
You were right. The issue was with the code our vendor supplied for the
Tomcat client webapp making outbound HTTPS connections. This was not
correctly overriding classes with the result that the truststore and
keystore environment settings were being completely ignored.
Thanks for your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Diarmuid,
(Marking as OT because this is not a Tomcat issue.)
On 9/1/15 5:34 PM, dmccrthy wrote:
> Sorry for the ambiguity, we're using scenario (b), outgoing client
> connections. The server cert is signed by GeoTrust but we don't
> have the full
