Serf / libsvn_ra_serf doesn't work with Squid-fronted Apache

14 views
Skip to first unread message

Arfrever Frehtes Taifersar Arahesis

unread,
Oct 12, 2008, 7:24:02 PM10/12/08
to Subversion Development, Serf Development
Serf / libsvn_ra_serf doesn't work with Squid-fronted Apache:

$ svn ls http://overlaystest.gentoo.org/svn/proj/python
svn: XML parsing failed: (411 Length Required)
$

This problem was originally reported in:
https://bugs.gentoo.org/show_bug.cgi?id=241234

Robin Johnson <rob...@gentoo.org> wrote in that bug report:
> Doing a tcpdump on during the co request, and comparing the requests, the Neon
> version sends PROPFIND with Content-Length, while serf sends PROPFIND without
> Content-Length, which thus upsets squid.

--
Arfrever Frehtes Taifersar Arahesis

signature.asc

Lieven Govaerts

unread,
Oct 13, 2008, 7:30:24 AM10/13/08
to Arfrever Frehtes Taifersar Arahesis, Subversion Development, Serf Development

The cause of this problem is that serf uses chunked encoding, a HTTP/1.1
feature that Squid doesn't support:
http://wiki.squid-cache.org/Features/HTTP11?highlight=%28chunked%29

While adding HTTP/1.0 fallback in serf has been discussed, no one is
working on it.

There are two workarounds:
- use ra_neon instead of ra_serf.
- switch from squid to a HTTP/1.1 proxy, like apache+mod_proxy.

I've updated serf issue 28 at
http://code.google.com/p/serf/issues/detail?id=28 to keep track of this
issue.

Lieven

Reply all
Reply to author
Forward
0 new messages