Return-Path: Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org Received: (qmail 762 invoked from network); 14 May 2005 09:48:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 May 2005 09:48:45 -0000 Received: (qmail 89033 invoked by uid 500); 14 May 2005 09:53:10 -0000 Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org Received: (qmail 89009 invoked by uid 500); 14 May 2005 09:53:09 -0000 Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "HttpClient Project" Reply-To: "HttpClient Project" Delivered-To: mailing list httpclient-dev@jakarta.apache.org Received: (qmail 88994 invoked by uid 99); 14 May 2005 09:53:09 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 14 May 2005 02:53:09 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 0C0052E1; Sat, 14 May 2005 11:48:40 +0200 (CEST) From: bugzilla@apache.org To: httpclient-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 34909] - Digest authentication problem with domain\user username format X-Bugzilla-Reason: AssignedTo Message-Id: <20050514094840.0C0052E1@ajax.apache.org> Date: Sat, 14 May 2005 11:48:40 +0200 (CEST) X-Virus-Checked: Checked X-Spam-Rating: minotaur.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://issues.apache.org/bugzilla/show_bug.cgi?id=34909 ------- Additional Comments From olegk@apache.org 2005-05-14 11:48 ------- I did some further research. I am certain that given the same auth challenge and the same cnonce value both HttpClient versions produce the same credentials hash ('response' attribute). The only obvious difference is slightly different arrangement of attributes in the auth response. I do not think this should matter but currently this is the only plausible theory that can explain the failure HttpClient 2.0: =============== Digest username="domain\username", realm="Digest", nonce="b2a83a38cd57c501af3ad2c91f189512060524424ffc2b818c9920db15cd247a9d47cf5a789d63c6", uri="/", qop="auth", algorithm="MD5-sess", nc=00000001, cnonce="a9b7ba70783b617e9998dc4dd82eb3c5", response="22c567093b3689e1edf4184fad8218d3", opaque="1704373a505e74c4ec692978e5c1a539" HttpClient 3.0: =============== Digest username="domain\username", realm="Digest", nonce="b2a83a38cd57c501af3ad2c91f189512060524424ffc2b818c9920db15cd247a9d47cf5a789d63c6", uri="/", response="22c567093b3689e1edf4184fad8218d3", qop="auth", nc=00000001, cnonce="a9b7ba70783b617e9998dc4dd82eb3c5", algorithm="MD5-sess", opaque="1704373a505e74c4ec692978e5c1a539" Oleg -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org