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 J
Philip Martin 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 wi
Philip Martin writes:
> If you run something like:
>
>curl -H - http://server/repository
>
> the Server line might identify the proxy.
Oops! Wrong option.
curl -I http://server/repository
or perhaps
curl -i -X PROPFIND http://server/repository
or perhaps visit
http://server/
Josh Geller writes:
> Get this message when attempting to commit either through svn command
> line (1.8.0) or TortoiseSVN 1.8.0. This is a working set that was
> upgraded from svn 1.7, and the server is a hosted svn on atlassian.net
> which is Subversion version 1.6.11 (r934486). Others are havin
Get this message when attempting to commit either through svn command line
(1.8.0) or TortoiseSVN 1.8.0. This is a working set that was upgraded from svn
1.7, and the server is a hosted svn on atlassian.net which is Subversion
version 1.6.11 (r934486). Others are having the same problem here:
