Hi P, Thanks for response.
I am refering two way SSL not just one way. In two way SSL, tomcat not only
needs to trust server's root CA also it needs to pass its signed certificate to
the server so server can recognize it.
My experience for setting up Webshpere as 2 ways SSL client, it did
Are you sure it's Tomcat doing the caching? I've found that both Firefox
and IE will cache CGI, JSP, servlet, and other dynamic results.
yes, i'm approaching certain that it isn't a browser issue. If i delete the
static files and thus force the system to regen i get updated data, but the
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
From: swoodbury [mailto:swoodb...@att.net]
Subject: Re: tomcat caching of static files
So the only thing left as far as i can see is the tomcat
server caching the file in memory and not noticing the
timestamp change when the thread re-creates the file.
Or some intermediary device between
Greetings,
We're developing an application on top of Tomcat. Our incoming
connections are always HTTPS. We've been using the self signed cert
that came with tcServer for testing, but now I'm trying to get our setup
working with an officially signed certificate we just got from GoDaddy.
I see. I guess I will look into using apache httpclient or some other library
(any recommendation?).
Webshpere actually takes care of outbound SSL connection by configuration (no
extra coding) that's why I got confused.
Thanks for input, Chuck.
YF
From: chuck.caldar...@unisys.com
To:
On Sat, Aug 7, 2010 at 2:20 PM, Steve Johnson st...@parisgroup.net wrote:
I've followed the GoDaddy instructions for adding a total of 4 certs (root +
2 intermediates + ours) to a fresh keystore file.
Do the GoDaddy instructions look anything like the Tomcat ones? :-)
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.
It may be that you have to do some configuration of your JDK and
environment to have SSL
The GoDaddy instructions mostly talk about building the keystore file,
and are very similar to that section of the document you mention. I
assume what you're getting at is that the instructions you mention might
be helpful to me. I have, unfortunately, been over those instructions
backwards
I apologize for the wall of text.
I'm working through the clustering and farm deployment documentation
for Tomcat 6 / Tomcat 7. To that end I've set up a 3 node cluster load
balanced by an Apache web server on a single system.
The environment and configuration particulars are at the end of the
On Sat, Aug 7, 2010 at 3:32 PM, Steve Johnson st...@parisgroup.net wrote:
I went through those instructions when I first got SSL working. I had SSL
working fine. All I did this time around was replace one keystore file
(tcserver.keystore) with another. I used the same password and alias
11 matches
Mail list logo
