"C. Michael Pilato" <cmpilato_at_collab.net> wrote on 03/31/2009 11:47:32 AM:
> 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.)
If you are on Windows, you can use the fiddler2 web debug proxy to trace
(and decode the SSL) traffic after setting up it's port to be your
subversion
proxy host. It is really nice because it parses out the header
information
and shows timing and return code information.
http://www.fiddler2.com/fiddler2/
Kevin R.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1498125
Received on 2009-03-31 19:55:05 CEST