Re: Apache-SSL or Mod-ssl

[Sam Newman]

Well, at the time I had been trying to use Apache-SSL, whci is the method for SSL mentioned in the tomcat docs so I assumed was the best one to use. Needless to say i cou;dnt get the sod to work. I tried using mod_ssl after finding that stronghold uses it. I got mod_ss l working so I guess I'll use that. As to why anyone would use strongolhd, the fact that it doesn't involve rebulidng apache, and that it comes with commercial support will be enough for a lot of people.   sam ----- Original Message ----- From: GOMEZ Henri To: [EMAIL PROTECTED] Sent: Tuesday, April 17, 2001 10:22 AM Subject: RE: Apache-SSL or Mod-ssl   I was wondering which is the prefered choice for work with servlets? I am having untold trouble getting Apache-SSL to work (built it, can't view a page without a seg fault). Whilst not a tomcat specific issue Apache-SSL is the mentioned way to get SSL working with tomcat. I've just tried RedHats Stronghold product (try www.c2.net) which gave be an out of the box SSL working Apache server (uses mod_ssl) in under 10 minutes. Getting tomcat to work with it hasn't been a problem either - well, hardly a problem (see my other post). Before I try and get my boss to buy stronghold, are there any issues I should be aware of with using mod_sll as opposed to Apache-SSL?   Why buy StrongHold ? Just use apache and mod_ssl directly .   If you're running Redhat 7.0 (maybe also in the announced 7.1), mod_ssl is built-in.   You could also go to ftp://ftp.falsehope.com/home/gomez/apache/ and grab latest apache 1.3.19 for Redhat 7.0 or ftp://ftp.falsehope.com/home/gomez/apache-mod_ssl/  for Redhat 6.x