Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of deltarho2k@gmail.com designates
 209.85.213.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=J6Yi+82miHABc/paQaLdWXn9YudvpjqwXMavt5KWegKpswETv/8ajKJsk5CuNTELYv
         vDwhR1fHgGjwfJWp1ef3no8X9f/I3f5Agt/75JZr8UyZ03vbFlRLd6hFOr6f3v+s9+4P
         dMP+qrpLj1HxXNof56Q8PfYco0nHC2rUpmPBY=
MIME-Version: 1.0
In-Reply-To: <4D768546.9080807@hanik.com>
References: <AANLkTinFGsHdZRhWbPTmiwGPyPQKiYVk04Z=S49e8+Ou@mail.gmail.com>
	<4D768546.9080807@hanik.com>
Date: Tue, 8 Mar 2011 14:50:43 -0500
Message-ID: <AANLkTikNLrRYO=ZxkrK3aMF1oZWi9GdZDjXcwpTcPT3s@mail.gmail.com>
Subject: Re: SSL on Apache 6.0.18 troubles
From: Jacob Nyhart <deltarho2k@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001636284cdc7cf049049dfded56

--001636284cdc7cf049049dfded56
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

That fixed it. Well, I feel officially dumb knowing the solution was that
simple and staring me right in the face... ./facepalm
Thanks for your quick response!
~J

On Tue, Mar 8, 2011 at 2:36 PM, Filip Hanik - Dev Lists
<devlists@hanik.com>wrote:

> add
>
> SSLEnabled=3D"true"
>
> to your connector
>
> Filip
>
>
> On 3/8/2011 12:20 PM, Jacob Nyhart wrote:
>
>> I am running Apache version 6.0.18 on a Windows 2003 server. Cannot go t=
o
>> 6.0.29 yet because of vendor/client requirements.
>>
>>
>>
>> I am attempting to setup SSL, but am not having any success and so I see=
k
>> your help.
>>
>>
>>
>> My connector in my settings.xml file looks like this:
>>
>>
>>
>>                   <Connector port=3D"443" maxHttpHeaderSize=3D"8192"
>>
>>
>> maxThreads=3D"150" minSpareThreads=3D"25" maxSpareThreads=3D"75"
>>
>>
>> enableLookups=3D"false" disableUploadTimeout=3D"true"
>>
>>
>> acceptCount=3D"100" scheme=3D"https" secure=3D"true"
>>
>>
>> clientAuth=3D"false" sslProtocol=3D"TLS"
>>
>>
>>  keystorePass=3D"xxxxxxxx"
>>
>>
>>  keystoreType=3D"PKCS12"
>>
>>
>>  keystoreFile=3D"path/to/my/pfx file" />
>>
>>
>>
>> The pfx file was generated by exporting my certificate from the IIS on t=
he
>> same server. That cert was generated from our company=92s internal CA (l=
ower
>> level environment).
>>
>>
>>
>> Now, here=92s the problem=85  If I call my app like this:  http://domain=
:8080
>> -- it works
>>
>> If I call my app like this:  http://domain:443 =96 it works, but I don=
=92t
>> suspect this is SSL traffic since the browser doesn=92t present any
>> indication
>> the traffic is secure.
>>
>> If I call my app like this: https://domain =96 it fails =96 reporting th=
at IE
>> cannot display the page. (the file being called is a *jsp file).
>>
>>
>>
>> The server is inside a firewalled DMZ, and I have confirmed with my
>> network
>>
>> guys that the rule is open. In addition, I have tested this from the
>> server
>>
>> itself, so firewall rules should not be an issue.
>>
>>
>>
>> The STDOut.log file and Windows Event Viewers are giving no indications =
as
>> to what the problem is, the Tomcat appears to start fine, and APorts sho=
ws
>> that Tomcat6 is listening on port 443.
>>
>>
>>
>> Any help would be appreciated.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


--=20
~J

--001636284cdc7cf049049dfded56--