Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD831C06A for ; Fri, 21 Jun 2013 14:24:07 +0000 (UTC) Received: (qmail 14652 invoked by uid 500); 21 Jun 2013 14:24:06 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 14587 invoked by uid 500); 21 Jun 2013 14:24:04 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 7340 invoked by uid 99); 21 Jun 2013 14:22:04 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of veriwell@veriwell.com.br designates 46.105.53.188 as permitted sender) Message-ID: <51C4616D.7090102@veriwell.com.br> Date: Fri, 21 Jun 2013 11:21:33 -0300 From: "Camilo S. Tsumanuma" User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: users@subversion.apache.org Subject: [TSVN and svn 1.8.0] Cannot Digest Authenticate. Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Dear Subversion Users Forum, I compiled subversion 1.8.0 in CentOS 6.4 using http://comments.gman​e.org/gmane.comp.ver​sion-control.subvers​ ion.user/113594 as guideline. I just used my own previous Apache Server configuration of Digest Authentication for WebDav SVN but it failed like described in Discussion Topic of TortoiseSVN Users Forum http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3058687. I cannot update, commit or checkout a working copy because I cannot authenticate. The 1.8.0 SVN clients repeatdly asks for username/password. It seems to be related to serf library at client side and may be HTTPS simultaneously. The Server seems to be very OK. Because I can Digest authenticate to the 1.8.0 Server using browser like Firefox, IE or Chrome and also with TortoiseSVN 1.7.13. Can you please help me with this? Should I open a new issue? Is this a known bug? I could find some discussion about serf 1.2.0 blocking 1.8.0 SVN release because of Digest Authentication. But I could not track if the used 1.2.1 serf library in 1.8.0 clients really solves the issue, and I don't know if I found a new bug. I can Basic authenticate using both 1.7.13 and 1.8.0 clients to the same server/repository/HTTPS using alternative URL/Apache . Thank you in advance, Camilo