On Wed, Sep 02, 2009 at 04:40:34PM +0200, Jelmer Vernooij wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jelmer Vernooij wrote:
> > The subversion client seems to have trouble parsing data sent by
> > mod_dav_svn in some rare cases. The HTTP layer appears to be
> > working fine, but parsing the XML data received fails. Two concrete
> > cases I have seen so far:
> >
> > - Certain (XML-invalid?) characters in commit messages seem to
> > cause problems. E.g.:
> >
> > svn log -v -r748 http://fbc.svn.sourceforge.net/svnroot/fbc (pcap
> > trace at http://samba.org/~jelmer/subversion-http-200-ok.cap)
> >
> > Depending on whether you're using neon or serf you'll get a
> > different error.
> >
> > serf gives: svn: XML parsing failed: (411 Length Required) neon
> > gives: svn: REPORT of '/svnroot/fbc/!svn/bc/748': 200 OK
> > (http://fbc.svn.sourceforge.net)
> >
> > - forward slashes (/) in svn property names. E.g.:
> >
> > svn ls -r45181 http://codespeak.net/svn/pypy/dist (pcap trace at
> > http://samba.org/~jelmer/subversion-http-slash-propname.cap)
> >
> > In this particular case the property named
> > "bzr:revision-id-v3:single-pypy/dist" is problematic.
> >
> > serf gives: svn: XML parsing failed: (411 Length Required) neon
> > gives: svn: PROPFIND of '/svn/!svn/bc/45181/pypy/dist': 207 Unknown
> > (http://codespeak.net)
> >
> > Should these issues be considered bugs in the client
> > implementations (they should be more liberal in what they accept),
> > in mod_dav(_svn) (it should be more strict about what it sends) or
> > perhaps in both?
> Ping. Any chance somebody could comment on these two issues or try to
> reproduce them so I can report them in the bug tracker ?
>
> Cheers,
>
> Jelmer
Please file issues.
Thanks,
Stefan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2390216
Received on 2009-09-02 16:46:23 CEST