Thanks Chris, I appreciate it!
On Fri, Aug 14, 2009 at 10:30 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Josh,
>
> On 8/13/2009 2:38 PM, Josh Gooding wrote:
> > So I navigated to https://(domain).com and low and behold it w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh,
On 8/13/2009 2:38 PM, Josh Gooding wrote:
> So I navigated to https://(domain).com and low and behold it works :).
Glad it's working for you.
> Next few questions:
Well, it's your thread, so I guess hijacking isn't that big of a deal...
> #1
Ah, I am semi starting to understand now. I was able to use openssl to
convert my pfx to a pem file which is part of the battle. From what I have
read in the docs, I needed a .crt file as well, which I used the .txt file
that the hosting co provided to me. It's nothing but a plain text PGP
signa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh,
On 8/11/2009 4:47 PM, Josh Gooding wrote:
> ok back to the topic at hand here. I have removed httpd from my server,
> installed APR, and have gotten my cert file from my hosting company. it is
> in pfx format. Now I found some information on
ok back to the topic at hand here. I have removed httpd from my server,
installed APR, and have gotten my cert file from my hosting company. it is
in pfx format. Now I found some information on the net:
http://tp.its.yale.edu/pipermail/cas/2005-July/001337.html
It was saying that I can just us
nevermind, I think I made some headway on this and will ask this over on the
httpd list. Thank you for getting me this far, I really appreciate it.
On Wed, Aug 5, 2009 at 8:50 AM, Josh Gooding wrote:
> *Andre wrote:
>
> The above is assuming that you would want all accesses which eventually go
*Andre wrote:
The above is assuming that you would want all accesses which eventually go
to Tomcat, to be under SSL from the client point of view.
The idea is : SSL creates an overhead (encryption). If the link between
Apache and Tomcat is secure (such as, they both run on the same host, or
they
Josh Gooding wrote:
Update:
So after re-re-reading the docs, since TC is not my standalone webserver, I
should configure Apache (httpd) for SSL. That seems to be what I am
reading.
Yes.
Client -> SSL -> Apache -> Ap/To Connector -> non-SSL -> Tomcat
(e.g. mod_jk)
Update:
So after re-re-reading the docs, since TC is not my standalone webserver, I
should configure Apache (httpd) for SSL. That seems to be what I am
reading.
On Tue, Aug 4, 2009 at 3:43 PM, Josh Gooding wrote:
> wait a sec here. I'm a little confused. Let me ask it this way. I have a
> L
wait a sec here. I'm a little confused. Let me ask it this way. I have a
Login.jsp file that takes uname / pwd and uses j_security_check for
authentication. That is the only thing that I want HTTPS on. Everything
else is not important.
I have setup Apache (httpd) and am forwarding the 1 html
I thought that you only had to set up on apache (httpd server). Thats the
way I got it working.
see
http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html#SSL%20and%20Tomcatrelevenat
excet below
*SSL and Tomcat*
*It is important to note that configuring Tomcat to take advantage of secure
sockets
> Just an update. I decided to change up what I was doing. Instead of
> starting with SSL on tomcat, I ported Apache and Tomcat to work together on
> my local test server. Now I am going to do the APR. Do I need to configure
> SSL on both Apache and Tomcat or just Tomcat?
If all connections go
Just an update. I decided to change up what I was doing. Instead of
starting with SSL on tomcat, I ported Apache and Tomcat to work together on
my local test server. Now I am going to do the APR. Do I need to configure
SSL on both Apache and Tomcat or just Tomcat?
On Mon, Jul 27, 2009 at 12:08
Thanks all, I appreciate the input. I used
http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html to attempt to
configure SSL. I'll read up on APR.
On Sat, Jul 25, 2009 at 6:14 AM, Mark Thomas wrote:
> Josh Gooding wrote:
> > One more thing. Here is my server.xml information that is relative:
Josh Gooding wrote:
> One more thing. Here is my server.xml information that is relative:
>
> SSLEngine="on" SSLRandomSeed="builtin" />
Looks like you are trying to use the APR connector.
> minSpareThreads="5" maxSpareThreads="75"
Neither of those two attributes are valid for Tomcat 6
Josh Gooding wrote:
One more thing. Here is my server.xml information that is relative:
On Fri, Jul 24, 2009 at 10:25 PM, Josh Gooding wrote:
Hello again.
Now that I have deployed my project on Tomcat 6.0.18 with a MySQL 5.1 db, I
need to clamp the server down tight using SSL. I've
One more thing. Here is my server.xml information that is relative:
On Fri, Jul 24, 2009 at 10:25 PM, Josh Gooding wrote:
> Hello again.
>
> Now that I have deployed my project on Tomcat 6.0.18 with a MySQL 5.1 db, I
> need to clamp the server down tight using SSL. I've already created my
>
Hello again.
Now that I have deployed my project on Tomcat 6.0.18 with a MySQL 5.1 db, I
need to clamp the server down tight using SSL. I've already created my
keystore file and I am able to get the server to serve on port 443 (by going
to http://localhost:443). I can get it to Subsequent attemp
18 matches
Mail list logo
