Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 31 Oct 2005 21:31:11 +0000
From: Colm MacCarthaigh <colm@stdlib.net>
To: dev@httpd.apache.org
Subject: Re: [PATCH] IPv6: strip zone-id from hostname
Message-ID: <20051031213111.GA23398@stdlib.net>
Reply-To: colm@stdlib.net
References: <1404e5910510311323m1ec04631y86764e64ba45e39a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1404e5910510311323m1ec04631y86764e64ba45e39a@mail.gmail.com>
User-Agent: Mutt/1.5.9i

On Mon, Oct 31, 2005 at 04:23:49PM -0500, Eric Covener wrote:
> If httpd receives a connection on a link-local (perhaps site-local?)

Only link-local, site-local won't matter (as is decrecated in unicast at
least).

> IPv6 socket, apr_getnameinfo()/ap_get_remote_host() can/will return
> something like the following: myv6host.xyz.com%bge0

yes :)

> There doesn't appear to be a way to tell the resolver not to append the zone.

Nor should there be, it's part of the unique identification of the
origin.

> This can trip up mod_auth_access/mod_authz_host/others? when
> performing a domain name match (Allow/Deny would have to be encoded
> with interface names to match the return value of getnameinfo())

link local addresses should absolutely not be appearing in DNS, and it
doesn't make much sense for them to be doing so. I would class this
as a non-problem.

When connected to on a link-local address, httpd should log the origin
with the interface-id intact, otherwide there'd be no way to determine
the origin on a multi-homed server :) 

> If httpd should be agnostic wrt zones, should ap_get_remote_host strip
> off anything following a percent symbol?

It shouldn't, and no :)

-- 
Colm MacC�rthaigh                        Public Key: colm+pgp@stdlib.net