Daniel Shahaf <danie...@elego.de> writes: > C. Michael Pilato wrote on Fri, May 31, 2013 at 10:30:58 -0400: >> 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. > > The 207 Multi-Status response might have contained > a <status>401</status> in the response body.
If your 1.7 client is using neon (the default) but also has serf support then using --config-option servers:global:http-library=serf will cause the 1.7 client to use serf which may help narrow down the problem. It doesn't help that this is another instance of a serf error number leaking into a Subversion error: http://subversion.tigris.org/issues/show_bug.cgi?id=4368 Ways to get a network trace: http://subversion.apache.org/docs/community-guide/debugging.html#net-trace -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
