From users-return-235395-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Tue Jul 10 16:42:11 2012 Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B40849DDD for ; Tue, 10 Jul 2012 16:42:11 +0000 (UTC) Received: (qmail 52558 invoked by uid 500); 10 Jul 2012 16:42:07 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 52506 invoked by uid 500); 10 Jul 2012 16:42:07 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 52496 invoked by uid 99); 10 Jul 2012 16:42:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 16:42:07 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [76.96.59.212] (HELO qmta14.westchester.pa.mail.comcast.net) (76.96.59.212) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 16:42:00 +0000 Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta14.westchester.pa.mail.comcast.net with comcast id YfFo1j0021swQuc5Eghfz5; Tue, 10 Jul 2012 16:41:39 +0000 Received: from Christophers-MacBook-Pro.local ([107.3.88.58]) by omta15.westchester.pa.mail.comcast.net with comcast id YghY1j0191FXhpX3bghZTP; Tue, 10 Jul 2012 16:41:33 +0000 Message-ID: <4FFC5B42.70207@christopherschultz.net> Date: Tue, 10 Jul 2012 12:41:38 -0400 From: Christopher Schultz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: How to support IPv6 on Apache Tomcat Version 7.0.22 References: In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aditi, On 7/9/12 5:37 AM, Aditi Sinha wrote: > I could get the comparison of the three connectors here > http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Connector_Comparison > > With the BIO connector specified, the server is not responding to > the https request. Is it because SSL Handshake is Blocking for BIO > connector? Everything is blocking for the BIO connection -- that's what the "B" stands for. > We need to support SSL. Is there a way to have below configuration > support IPv6? I can't see a reason why you can't use SSL over any of the connectors. What happens when you try to connect? Note that AJP never supports HTTPS (at least not directly -- the web proxy must terminate the SSL connection, but can forward the details like cipher, client certificate, etc. to Tomcat and your webapp). > HTTP Connector: NIO protocol > AJP Connector: APR protocol/NIO protocol. That should be all that is necessary. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/8W0IACgkQ9CaO5/Lv0PA0RwCfe8hWScXATo/pPjBCcsGCwWi5 jYgAoKRjazQPQkEe0T1vwlvulMc/kgk5 =k0tm -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org