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

Re: more problems when using serf

From: Michael Ching <michaelc_at_wush.net>
Date: Tue, 25 May 2010 15:32:21 +0000 (UTC)

Mark Phippard <markphip <at> gmail.com> writes:

> > with serf leads to:
> >
> > svn: The PROPFIND response did not include the requested resourcetype value
> >
>
> Aren't they just emulating a Subversion server and the Subversion
> protocol? They have probably just not implemented it correctly.

This error can be caused by a reverse proxy or load balancer which does
not support chunked requests. We show the same errors when requests are
proxied through either nginx or squid.

You can work around the issue by proxying through apache+mod_proxy
(which supports HTTP 1.1), but serf 0.30 does not proxy https requests
correctly (it talks ssl to the proxy server instead of issuing a CONNECT
request).

serf really should support a proper fallback to HTTP 1.0 before becoming
the default library, as using a reverse proxy in front of svn is a
common setup and very few of them support HTTP 1.1.
Received on 2010-05-25 17:35:43 CEST

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