Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 50957 invoked from network); 24 Mar 2008 12:24:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Mar 2008 12:24:39 -0000 Received: (qmail 80557 invoked by uid 500); 24 Mar 2008 12:24:33 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 80544 invoked by uid 500); 24 Mar 2008 12:24:33 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 80533 invoked by uid 99); 24 Mar 2008 12:24:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 05:24:33 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of xyon@indigorobot.com designates 72.156.224.172 as permitted sender) Received: from [72.156.224.172] (HELO indigorobot.com) (72.156.224.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 12:23:44 +0000 Subject: Re: modperl with SSL From: xyon To: modperl In-Reply-To: <20080324114657.GA22355@connexer.com> Content-Type: text/plain; charset=utf8 Date: Mon, 24 Mar 2008 08:23:51 -0400 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -4.4 (----) X-Spam-Report: Spam detection software, running on the system "ettinsmoor.indigorobot.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I also recommend stunnel. It has come through for me in these same situations without problems. On Mon, 2008-03-24 at 07:46 -0400, Roberto C. Sánchez wrote: > On Mon, Mar 24, 2008 at 03:25:26PM +0800, J. Peng wrote: > > hello list, > > > > we have our own realserver called QHttpd. > > This realserver doesn't support SSL protocal (https). > > So I have to develop a proxy before QHttpd to get it be compatible with SSL. > > I was thinking using modperl handler to do it. > > modperl accept the SSL connection from clients, do the verification, > > and if it's valid, redirect it to realserver with non-SSL (common > > http) protocal. > > Is it possible? if so, how to begin with it? at which stage? > > Thanks in advance. > > > Would something like iprelay or stunnel not be sufficient for your > needs? > > Regards, > > -Roberto [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Message-Id: X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: YES I also recommend stunnel. It has come through for me in these same situations without problems. On Mon, 2008-03-24 at 07:46 -0400, Roberto C. S=C3=A1nchez wrote: > On Mon, Mar 24, 2008 at 03:25:26PM +0800, J. Peng wrote: > > hello list, > >=20 > > we have our own realserver called QHttpd. > > This realserver doesn't support SSL protocal (https). > > So I have to develop a proxy before QHttpd to get it be compatible with= SSL. > > I was thinking using modperl handler to do it. > > modperl accept the SSL connection from clients, do the verification, > > and if it's valid, redirect it to realserver with non-SSL (common > > http) protocal. > > Is it possible? if so, how to begin with it? at which stage? > > Thanks in advance. > >=20 > Would something like iprelay or stunnel not be sufficient for your > needs? >=20 > Regards, >=20 > -Roberto