Return-Path: <mike_moran@mac.com>
Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org
Received: (qmail 3890 invoked from network); 27 Feb 2003 18:54:47 -0000
Received: from smtpout.mac.com (17.250.248.86)
  by daedalus.apache.org with SMTP; 27 Feb 2003 18:54:47 -0000
Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66])
	by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h1RIspGs012373
	for <commons-httpclient-dev@jakarta.apache.org>;
 Thu, 27 Feb 2003 10:54:51 -0800 (PST)
Received: from mac.com ([194.105.183.41]) by asmtp02.mac.com
          (Netscape Messaging Server 4.15) with ESMTP id HAZDVE00.QEN for
          <commons-httpclient-dev@jakarta.apache.org>; Thu, 27 Feb 2003
          10:54:50 -0800
Message-ID: <3E5E5EEB.6020209@mac.com>
Date: Thu, 27 Feb 2003 18:54:35 +0000
From: Mike Moran <mike_moran@mac.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Commons HttpClient Project <commons-httpclient-dev@jakarta.apache.org>
Subject: Re: DO NOT REPLY [Bug 10807]  -     Handle virtual hosts, relative
 urls, multi-homing
References: <20030227183718.13596.qmail@nagoya.betaversion.org>
In-Reply-To: <20030227183718.13596.qmail@nagoya.betaversion.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

bugzilla@apache.org wrote:
[ ... ]

>
>
>------- Additional Comments From becke@u.washington.edu  2003-02-27 18:37 -------
>I'd like to go ahead and tackle this one, but I need a little clarification. 
>Does the following correctly describe what we want?
>
>- we want to perform a get on www.google.com, let's say www.google.com has X > 1
>IP addresses 
>- we want to specify which IP address x to actually connect to
>- we want www.google.com in the Http header instead of x
>
>If this is the case, it sounds like we may want support for custom DNS
>resolution.  Though this might be a little more than is needed for this simple
>case I think that is what it boils down to.
>
I would support addition regardless, but then that's just me. I assume 
by "custom DNS resolution" you mean passing in the resolved values eg 
the HttpClient library is told: "here's the Name/IP mapping, do a GET to 
this IP with this Host: <Name>"?

-- 
Mike