Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 30358 invoked from network); 10 Jun 2008 01:19:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jun 2008 01:19:41 -0000 Received: (qmail 42119 invoked by uid 500); 10 Jun 2008 01:19:41 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 42063 invoked by uid 500); 10 Jun 2008 01:19:41 -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 42052 invoked by uid 99); 10 Jun 2008 01:19:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2008 18:19:41 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryan-apache@trolocsis.com designates 64.62.244.66 as permitted sender) Received: from [64.62.244.66] (HELO zeus.kimaker.com) (64.62.244.66) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jun 2008 01:18:52 +0000 Received: by zeus.kimaker.com (Postfix, from userid 1002) id D5A6E75843C; Mon, 9 Jun 2008 18:19:09 -0700 (PDT) Date: Mon, 9 Jun 2008 18:19:09 -0700 From: Ryan Phillips To: dev@httpd.apache.org Subject: Re: [patch] Add IPV6 'specials' flag to mod_rewrite Message-ID: <20080610011909.GB40239@zeus.kimaker.com> Mail-Followup-To: dev@httpd.apache.org References: <20080609230715.GA40239@zeus.kimaker.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080609230715.GA40239@zeus.kimaker.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Checked: Checked by ClamAV on apache.org Ryan Phillips said: > So I needed to create some mod_rewrite rules only for IPv6 when httpd is > configured for both ipv4 and ipv6 modes. This patch adds > 'RewriteCond IPV6 on' support to the ruleset. > > I initially tried to see if the incoming socket was APR_INET6, but couldn't > find the right structure within the request to query. > Should r->connection->local_addr or remote_addr have the correct socket family? If I try either of these over an IPv4 connection, I always get a socket family of IPv6. -Ryan