Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 19524 invoked from network); 15 Apr 2002 23:23:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Apr 2002 23:23:15 -0000 Received: (qmail 19249 invoked by uid 97); 15 Apr 2002 23:23:20 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 19232 invoked by uid 97); 15 Apr 2002 23:23:19 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 19218 invoked by uid 50); 15 Apr 2002 23:23:19 -0000 Date: 15 Apr 2002 23:23:19 -0000 Message-ID: <20020415232319.19217.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 8135] New: - Exception shouldn't be thrown for unsupported authentication method X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8135 Exception shouldn't be thrown for unsupported authentication method Summary: Exception shouldn't be thrown for unsupported authentication method Product: Commons Version: 1.0 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: HttpClient AssignedTo: commons-dev@jakarta.apache.org ReportedBy: xiaowei@stratify.com Currently, Authenticator will throw an UnsupportedOperationException for unsupported authentication method (like NTLM). This is correct. However, HttpMethodBase.execute only catches HttpException, so this UnsupportedOperationException is leaked to the user. This is undesirable, because user may want a chance to handle such such authentication themself. The correct way is to pass the http status code to the user, just like how it treats redirect to a different host. The simple fix is to catch all exceptions in HttpMethodBase.execute when calling Authenticator.authenticate. -- To unsubscribe, e-mail: For additional commands, e-mail: