Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Sat, 2 Mar 2002 16:50:29 -0800
From: Justin Erenkrantz <jerenkrantz@ebuilt.com>
To: dev@httpd.apache.org
Subject: Re: cvs commit: apache-1.3/src/modules/proxy proxy_http.c
Message-ID: <20020303005029.GM24710@ebuilt.com>
Mail-Followup-To: Justin Erenkrantz <jerenkrantz@ebuilt.com>,
	dev@httpd.apache.org
References: <20020302130852.15753.qmail@icarus.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020302130852.15753.qmail@icarus.apache.org>
User-Agent: Mutt/1.5.0i

On Sat, Mar 02, 2002 at 01:08:52PM -0000, minfrin@apache.org wrote:
> minfrin     02/03/02 05:08:52
> 
>   Modified:    src      CHANGES
>                src/modules/proxy proxy_http.c
>   Log:
>   No idea why an HTTP/1.1 proxy would send an HTTP/1.0 request
>   to a remote server by default.

The question I think is whether the proxy module is truly
HTTP/1.1 compliant.  If it can handle anything a true HTTP/1.1
server can return *and* meet the proxy criteria set forth in
the RFC, then it can advertise itself as being 1.1.  Otherwise,
it should say it's 1.0.  -- justin

P.S.  Of course, this is a Roy question...