Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 43049 invoked from network); 4 May 2004 20:19:38 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 May 2004 20:19:38 -0000 Received: (qmail 61716 invoked by uid 500); 4 May 2004 20:19:22 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 61682 invoked by uid 500); 4 May 2004 20:19:22 -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 61599 invoked from network); 4 May 2004 20:19:21 -0000 Received: from unknown (HELO felix.lh.net.au) (203.149.69.43) by daedalus.apache.org with SMTP; 4 May 2004 20:19:21 -0000 Received: from [192.168.1.7] (ppp166-90.lns1.bne3.internode.on.net [150.101.166.90]) by felix.lh.net.au (Postfix) with ESMTP id 3FC3D59D0 for ; Wed, 5 May 2004 06:24:30 +1000 (EST) Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <4097862B.405@nose.ch> References: <825BF35A92B3F0479CC164ECBBE9376EE3B685@kccxoex06.corp.kpmgconsulting.com> <97E3E0CC-9DBF-11D8-963C-000A95B94038@intencha.com> <4097862B.405@nose.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <562707AE-9E08-11D8-963C-000A95B94038@intencha.com> Content-Transfer-Encoding: quoted-printable From: Adrian Sutton Subject: Re: IIS (NTLM) + proxy server (NTLM or basic) problem Date: Wed, 5 May 2004 06:19:24 +1000 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 It's already mentioned at=20 http://jakarta.apache.org/commons/httpclient/authentication.html : 3. NTLM authenticates a connection and not a request, so you need = to =20 authenticate every time a new connection is made and keeping the=20 connection open during authentication is vital. Due to this, NTLM=20 cannot be used to authenticate with both a proxy and the server, nor=20 can NTLM be used with HTTP 1.0 connections or servers that do not =20 support HTTP keep-alives. On 04/05/2004, at 10:01 PM, Ortwin Gl=FCck wrote: > Adrian Sutton wrote: >> There is absolutely no way that HttpClient can authenticate with both=20= >> an NTLM proxy and an NTLM host at the same time. The protocol just=20= >> doesn't allow for it, > > It would be worth mentioning that in a sentence or two in our=20 > authentication guide. > > --------------------------------------------------------------------- > To unsubscribe, e-mail:=20 > commons-httpclient-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail:=20 > commons-httpclient-dev-help@jakarta.apache.org > ---------------------------------------------- Intencha "tomorrow's technology today" Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org