Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 23376 invoked from network); 16 Feb 2007 21:46:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2007 21:46:28 -0000 Received: (qmail 55803 invoked by uid 500); 16 Feb 2007 21:46:31 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 55526 invoked by uid 500); 16 Feb 2007 21:46:30 -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 55515 invoked by uid 99); 16 Feb 2007 21:46:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2007 13:46:30 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of pharkins@gmail.com designates 64.233.162.234 as permitted sender) Received: from [64.233.162.234] (HELO nz-out-0506.google.com) (64.233.162.234) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2007 13:46:20 -0800 Received: by nz-out-0506.google.com with SMTP id x3so1043168nzd for ; Fri, 16 Feb 2007 13:45:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gRMmm2NkbjQ7Cf3D8d77np7UGxY+fS49QTUiGUCoqqhgHmCc8gLO+FOJtPtXvaexw5enR+zV2QBozVQBMK32uC3EQXSWNuUSCCg8iB3stc+tc4aEV3elARVZAYImMAQT83iEqklc1+Eavggzwvw4Bc2r3uBPfoqsjL10gmD0PhY= Received: by 10.65.224.11 with SMTP id b11mr5726166qbr.1171662359503; Fri, 16 Feb 2007 13:45:59 -0800 (PST) Received: by 10.65.250.9 with HTTP; Fri, 16 Feb 2007 13:45:59 -0800 (PST) Message-ID: <66887a3d0702161345p489044a1rd9af18e9e7f0ac14@mail.gmail.com> Date: Fri, 16 Feb 2007 16:45:59 -0500 From: "Perrin Harkins" To: "Steve Ensley" Subject: Re: mod_proxy post authentication with modified credentials Cc: modperl@perl.apache.org In-Reply-To: <31fabc220702161323w119dcbc8jd4008f50122cdd2b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <31fabc220702161323w119dcbc8jd4008f50122cdd2b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 2/16/07, Steve Ensley wrote: > What would a workable way to proxy this connection to the appserver > but providing the modified credentials. I can think of a few things that would probably work. You could make the proxy requests yourself, with LWP. You could hack the source of mod_proxy. You could run your auth translation code on the appserver, if it's an apache server that you have access to. You could also write your code as an input filter, changing the auth credentials before mod_proxy sees them. - Perrin