That is the problem here as well. We are using hosted svn from atlassian, so this may be affecting a lot of users. Here is the output with our server name changed:
$ curl -i -X PROPFIND https://ourserver.atlassian.net/svn/OurRepo
HTTP/1.1 401 Authorization Required
Server: nginx
Date: Mon, 24 Jun 2013 12:27:37 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
WWW-Authenticate: Basic realm="Subversion Repository"
Content-Length: 491
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Authorization Required</title>
</head><body>
<h1>Authorization Required</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.2.3 (CentOS) Server at ourserver.atlassian.net Port 80</addr
ess>
</body></html>
From: Philip Martin
Sent: Monday, June 24, 2013 7:28 AM
To: Josh Geller
Cc: users_at_subversion.apache.org
Philip Martin <philip.martin_at_wandisco.com> writes:
> Is there an nginx proxy in front of Apache? I suspect this is another
> case of the proxy not supporting chunked Transfer-Encoding, coupled with
> the bug in 1.8.0 that causes the client to treat a 411 error as success.
> When this happens svn_ra_serf__fetch_node_props will go on to produce
> the error you see.
I've installed nginx as a reverse proxy and I can confirm that it does
give exactly that error on commit.
--
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
www.wandisco.com
Received on 2013-06-24 14:31:51 CEST