Return-Path: Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org Received: (qmail 20888 invoked from network); 22 Dec 2004 16:57:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Dec 2004 16:57:10 -0000 Received: (qmail 94991 invoked by uid 500); 22 Dec 2004 16:56:45 -0000 Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org Received: (qmail 94965 invoked by uid 500); 22 Dec 2004 16:56:45 -0000 Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "HttpClient Project" Reply-To: "HttpClient Project" Delivered-To: mailing list httpclient-dev@jakarta.apache.org Received: (qmail 94941 invoked by uid 99); 22 Dec 2004 16:56:45 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from fire.nose.ch (HELO mail.nose.ch) (195.134.131.71) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 22 Dec 2004 08:56:40 -0800 Received: (qmail 3222 invoked by uid 1010); 22 Dec 2004 17:56:33 +0100 Received: from 192.168.1.7 by chekov (envelope-from , uid 89) with qmail-scanner-1.23st (clamdscan: 0.70. spamassassin: 2.64. perlscan: 1.23st. Clear:RC:1(192.168.1.7):. Processed in 0.045484 secs); 22 Dec 2004 16:56:33 -0000 X-qmail-scanner-Mail-From: ortwin.glueck@nose.ch via chekov X-qmail-scanner: 1.23st (Clear:RC:1(192.168.1.7):. Processed in 0.045484 secs Process 3214) Received: from unknown (HELO ?192.168.1.7?) (192.168.1.7) by chekov.nose.ch with AES256-SHA encrypted SMTP; 22 Dec 2004 17:56:33 +0100 Message-ID: <41C9A740.5000006@nose.ch> Date: Wed, 22 Dec 2004 17:56:32 +0100 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= Organization: NOSE Applied Intelligence User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HttpClient Project Subject: Re: NTLM crashing jCIFS v. 0.7.3 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Steve, I mean if jCIFS crashes for whatever reason, it is a jCIFS problem. Even if the NTLM implementation in HttpClient was faulty, jCIFS must gracefully handle the problem and issue an error message or something. But in no occasion must any application crash due to malformed input. If you have proof that HttpClient's NTLM implementation is faulty, we happily accept a bug report. Interesting enough, both HttpClient's as well as jCIFS' NTLM implementation are based on davenport.sf.net :-) Ortwin Gl�ck Steve Johnson wrote: > Hi Ortwin, > > You mean it is a problem with jCIFS v. 0.7.3, rather than > with the HttpClient classes NTLM.java or NTLMScheme.java? > If so, I see what you mean. > > Thanks for explaining, > > Steve Johnson, Software Engineer, sjohnson@mercury.com > direct 720.564.6532 > www.mercury.com --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org