[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: authentication error after upgrading client to svn1.8.0-rc2 (accessing a svn1.7.8 server)

From: Welch, Klaus <klaus.welch_at_advantest.com>
Date: Fri, 31 May 2013 14:45:40 +0000

________________________________________
From: C. Michael Pilato [cmpilato_at_collab.net]
Sent: Friday, May 31, 2013 4:30 PM
To: Welch, Klaus
Cc: users_at_subversion.apache.org
Subject: Re: authentication error after upgrading client to svn1.8.0-rc2 (accessing a svn1.7.8 server)

On 05/31/2013 09:53 AM, Klaus Welch wrote:
> I'not sure what a wiretrace is. I've inlined related pieces from apache logs.
>
> access.log:
> ::1 - - [31/May/2013:15:33:34 +0200] "OPTIONS * HTTP/1.0" 200 -
> xx.yy.zz.uu - - [31/May/2013:15:46:00 +0200] "OPTIONS /svn/xxx HTTP/1.1" 401
> 401
> xx.yy.zz.uu - aaa.bbb [31/May/2013:15:46:00 +0200] "OPTIONS /svn/xxx
> HTTP/1.1" 200 189
> xx.yy.zz.uu - aaa.bbb [31/May/2013:15:46:00 +0200] "OPTIONS /svn/xxx
> HTTP/1.1" 200 189
> xx.yy.zz.uu - aaa.bbb [31/May/2013:15:46:00 +0200] "PROPFIND
> /svn/xxx/!svn/rvr/9099 HTTP/1.1" 207 773

But you got the error on the client? I see no errors in this log at all.

That's why I'm not sure where to start looking into.

Error message complained about authentication but the correct account was logged in the access.log and
nothing in error.log (where usually such stuff is logged).

Setup is:
 * one shell
 * both clients (1.7.9 and 1.8.0-rc2) installed in parallel
 * doing the same operation with both
 * 1.7 binary ok, 1.8 binary fails

On monday I'll check the serf version, remove client side credential, carefully re-check all the build logs.

Hopefully something indicates where to look further.
 

Many thanks for your support.

With best regards,

Klaus

--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
Received on 2013-05-31 16:46:25 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.