Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 93834 invoked from network); 26 Mar 2004 13:44:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 26 Mar 2004 13:44:25 -0000 Received: (qmail 27372 invoked by uid 500); 26 Mar 2004 13:44:21 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 27320 invoked by uid 500); 26 Mar 2004 13:44:20 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 27303 invoked from network); 26 Mar 2004 13:44:20 -0000 Received: from unknown (HELO mxout1.cac.washington.edu) (140.142.32.134) by daedalus.apache.org with SMTP; 26 Mar 2004 13:44:20 -0000 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QDiLnK013141 for ; Fri, 26 Mar 2004 05:44:21 -0800 Received: from [10.0.1.2] (pool-141-149-173-21.bos.east.verizon.net [141.149.173.21]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QDiJe5016681 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Fri, 26 Mar 2004 05:44:20 -0800 Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Becke Subject: Re: Tunneling non-HTTP through a web proxy with HttpClient Date: Fri, 26 Mar 2004 08:44:13 -0500 To: "Commons HttpClient Project" X-Mailer: Apple Mail (2.613) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > Hi Mike & Mike :) > Since CONNECT is also an HTTP method, it is not totally > out of scope for the HttpClient. From RFC 2616, section 9.9: Agreed. CONNECT is definitely an HTTP method. The only question is if we should support it's use in non-HTTP contexts. > Maybe we can consider official support for CONNECT > as a feature for the big 4.0 API overhaul. It seems like it could be a good addition. My only hesitation is in giving direct access to the Socket. This seems like a pretty major departure from our current system. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org