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

Re: serf failure

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 31 Mar 2009 12:47:32 -0400

Ben Collins-Sussman wrote:
> Looking at the traffic in my first email answers both questions. :-)
>
> On Tue, Mar 31, 2009 at 10:05 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>
>> I didn't find root of the problem, but removing '!' character from
>> X-SVN-VR-Base header value solves the problem. Btw what is Apache
>> version on red-bean?
>
> Server: Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8g DAV/2
> SVN/1.5.6 PHP/5.2.9 mod_python/3.3.1 Python/2.5.4
>
>
> On Tue, Mar 31, 2009 at 10:10 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>
>> Seriously, though. I can checkout your kc-score location and update back
>> and forth between r676 and HEAD without problem using serf. What version of
>> libserf are you running?
>
> User-Agent: SVN/1.7.0 (dev build) serf/0.3.0

Doh!

I just ran into a completely reproducible and similarly looking problem
trying to update my svnbook working copy from Google Code. Unfortunately,
that's an SSL connection and no so trivially trace-able. (Still, couldn't
make the problem occur against your Winesburg repository tree.)

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1497599

Received on 2009-03-31 18:48:01 CEST

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

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