Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 865 invoked from network); 2 Apr 2009 22:31:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 22:31:58 -0000 Received: (qmail 54466 invoked by uid 500); 2 Apr 2009 22:31:56 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 54398 invoked by uid 500); 2 Apr 2009 22:31:56 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 54389 invoked by uid 99); 2 Apr 2009 22:31:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 22:31:56 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [72.167.82.89] (HELO p3plsmtpa01-09.prod.phx3.secureserver.net) (72.167.82.89) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Apr 2009 22:31:47 +0000 Received: (qmail 24054 invoked from network); 2 Apr 2009 22:31:24 -0000 Received: from unknown (76.252.112.72) by p3plsmtpa01-09.prod.phx3.secureserver.net (72.167.82.89) with ESMTP; 02 Apr 2009 22:31:24 -0000 Message-ID: <49D53C88.9010803@rowe-clan.net> Date: Thu, 02 Apr 2009 17:30:32 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Adopting mod_remoteip to modules/metadata/ ? References: <49D2AB2E.1050303@rowe-clan.net> <49D34A07.3090803@sharp.fm> In-Reply-To: <49D34A07.3090803@sharp.fm> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Graham Leggett wrote: > William A. Rowe, Jr. wrote: > >> I have essentially finished mod_remoteip at this point and am looking >> to find out the interest level of adopting this as a core module into >> trunk (modules/metadata/ appears to be the most appropriate target)? > > +1. That's two of us; I'm still looking for at least one more opinion. > I had to code up a similar feature recently in something that needed to > know the end user's IP address, this will be very useful for apps behind > load balancers and reverse proxies. I've heard similar from others, which is why this seems appropriate for the core distribution, even if it's not enabled by 'most'.