Ivan Zhakov <i...@visualsvn.com> writes: > On Tue, Jun 18, 2013 at 9:55 AM, Ben Reser <b...@reser.org> wrote: >> >> The 204 shouldn't be odd, that just means a response without content. >> > Most likely serf doesn't handle HTTP 204 response code and expect > message body, while server doesn't send it.
A 204 response is the normal behaviour after just about every failed commit, serf doesn't have a problem on my Linux box: $ svn ci -mm wc Sending wc/A/f Transmitting file data .svn: E155011: Commit failed (details follow): svn: E155011: File '/home/pm/sw/subversion/obj/wc/A/f' is out of date svn: E170004: Item '/A/f' is out of date DELETE /obj/repo/!svn/txn/2-3 HTTP/1.1\r Host: localhost:9630\r User-Agent: SVN/1.8.1-dev (x86_64-unknown-linux-gnu) serf/1.2.1\r DAV: http://subversion.tigris.org/xmlns/dav/svn/depth\r DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo\r DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops\r \r HTTP/1.1 204 No Content\r Date: Tue, 18 Jun 2013 11:04:35 GMT\r Server: Apache/2.2.22 (Debian) mod_ssl/2.2.22 OpenSSL/1.0.1e DAV/2 SVN/1.9.0-dev\r Content-Length: 0\r Content-Type: text/plain\r \r -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data www.wandisco.com
