-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve,
On 8/7/2010 6:24 PM, Steve Johnson wrote:
I can confirm that the Apache HTTPClient module is a good way to go.
In fact, it works with zero configuration. You simply give it a normal
'https' URL, and it does the right thing automagically.
take some
configuration in webshpere side.
Do anyone have similiar experience?
Thanks,
YF.
From: p...@pidster.com
Date: Fri, 6 Aug 2010 14:24:32 +0100
Subject: Re: Two-way SSL setup as Tomcat as a client
To: users@tomcat.apache.org
On 6 Aug 2010, at 13:12, yifeng wu yifen...@hotmail.com
From: yifeng wu [mailto:yifen...@hotmail.com]
Subject: RE: Two-way SSL setup as Tomcat as a client
I am refering two way SSL not just one way.
Irrelevant; Pid's statement still stands: it's your webapp, not Tomcat, that is
trying to communicate with an external server. Tomcat plays no role
To: users@tomcat.apache.org
Date: Sat, 7 Aug 2010 11:22:41 -0500
Subject: RE: Two-way SSL setup as Tomcat as a client
From: yifeng wu [mailto:yifen...@hotmail.com]
Subject: RE: Two-way SSL setup as Tomcat as a client
I am refering two way SSL not just one way.
Irrelevant; Pid's statement
: chuck.caldar...@unisys.com
To: users@tomcat.apache.org
Date: Sat, 7 Aug 2010 11:22:41 -0500
Subject: RE: Two-way SSL setup as Tomcat as a client
From: yifeng wu [mailto:yifen...@hotmail.com]
Subject: RE: Two-way SSL setup as Tomcat as a client
I am refering two way SSL not just one way.
Irrelevant
On 6 Aug 2010, at 13:12, yifeng wu yifen...@hotmail.com wrote:
Hi,
I am trying to make a call from Tomcat to another application server
(Websphere) and the communication channel is secured with two-way SSL.
I have been searching on the net for hours and cannot find the information
about
