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

Invalid characters over HTTP transport: client or server bug?

From: Jelmer Vernooij <jelmer_at_samba.org>
Date: Wed, 29 Jul 2009 04:18:39 +0200

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

serf gives: svn: XML parsing failed: (411 Length Required)
neon gives: svn: REPORT of '/svnroot/fbc/!svn/bc/748': 200 OK

- forward slashes (/) in svn property names. E.g.:

svn ls -r45181 http://codespeak.net/svn/pypy/dist
(pcap trace at

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?



Received on 2009-07-29 10:49:32 CEST

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