Subversion 1.8.0 client working against server 1.6.11

Question

I recently upgraded my subversion client to 1.8.0, even though our subversion server is 1.6.11, as I have verified everywhere that it looks like they should be compatible.

The main commands work fine (update, commit, etc.). The problem is that when I try to execute some more involved commands, such as moving, or I try to create a release from the maven release plugin. In such cases, I get the following error:

[ERROR] svn: E175002: Unable to connect to a repository at URL 'https://mycompaniesserver.com/svn/repo/trunk/project' [ERROR] svn: E175002: OPTIONS request on '/svn/repo/trunk/project' failed: 503 Service Unavailable 

That my fellow colleagues who use a number of clients from 1.6 to the last 1.7 do not seem to receive.

I assume that Subversion 1.8 sends HTTP OPTIONS commands that the old versions of the client did not have, and the subversion o proxy server firewall (and not the disruptive operation itself) rejects them.

Is there a way to prevent sending messages of newer formats, except to return to the older subversion client (since I already converted all my projects to 1.8 format)? Or is there a clear rule that you need to add to the subversion server firewall in order to work with 1.8 clients?

Edit: I returned to client 1.7.x and everything works fine, but I would really like to find a way that I could use client 1.8 without involving the sysadmin server.

Answer 1

I had the same problem with subversion 1.8.0 client through tortoisesvn 1.8.0 when connecting to subversion 1.5.1 server via https proxy. resolved it using an older version of the subversion client.

Answer 2

I suppose you can read the chapter "Neon-based HTTP client support has been removed" in the Subversion 1.8 release notes, note the server - and client-side configuration options for Skelta | Bulk and client-server test modes from the table (discuss Network Administrator with it) - you can move from an array to skelta with 1.8

Another version - proxies | firewal in the middle block

Unable to connect to repository by URL

new changed svn-client activity

when Kerberos or NTLM authentication is used ... add a 2-4 KB header to the HTTP request and response

Answer 3

IIRC is a bug in 1.8.0. Install one of the later releases 1.8.x.

Answer 4

There was this problem. It has nothing to do with the settings, that only the latest version of Tortoise does not work with the version of SVN installed on my server. I downloaded the previous version of Tortoise and the problem was resolved.

(had version 1.8, downloaded 1.7, and it worked. Interestingly, however, after upgrading SVN on the server to 1.8, Tortoise 1.8 still did not work, and I could only connect to Tortoise 1.7.

Answer 5

As another data point, I had a problem talking to server 1.6 from client 1.8 via http. There was some dodgy proxy server that claimed it met the requirements of 1.1. Subversion though does push the http protocol.

Client 1.7 has two http libraries: WebDAV and Serf. WebDAV was reset to 1.8, leaving you with only the Serf http library.

I needed to explicitly disable redistributed transfers in my svn 1.8 client configuration file. Then everything worked (except for all the checks that included the new file, sigh!).

See the first entry in Known Issues in version 1.8 and read the http-chunked-requests = no in your ~/.subversion/servers file

Answer 6

I am sure this question could be answered elsewhere. However, recently, while working on my project, I got the same problem and applied the solution given elsewhere, that is, commenting

the line above in the image did not work for me as it was already commented out. The FYI file is located on the local system as follows: strong text C: \ Documents and Settings_username_ \ Application Data \ Subversion \ servers

We used the Subversion eclipse plugin to perform all operations. The reason this happens is because the subversion request receives a proxy that does not support multiple HTTP methods.

As a solution, I did the following. In your Eclipse IDE

Go to Window> Preferences> Network Connections. If the value in "Active Provider:" is different from Direct, then change it to Direct. Repeat the operation, trying, and it should work like a charm. :-)

Answer 7

In my case, the following solution worked:

• Switch to

   %APPDATA%\Subversion\servers 

• Add an ad at the end of the following line:

    http-chunked-requests = no