Attempting to use the Git Subversion Bridge Against the Latest Subversion Client yields the following error:
Command: Update Updating: S:\My Downloads\Code\GitHub\ManipulativeReplacer from https://github.com/aolszowka/ManipulativeReplacer/trunk Error: Unable to connect to a repository at URL Error: 'https://github.com/aolszowka/ManipulativeReplacer/trunk' Error: The server at 'https://github.com/aolszowka/ManipulativeReplacer/trunk' does Error: not support the HTTP/DAV protocol Completed!:
This issue is poping up in various Subversion Communities as Developers Upgrade: https://groups.google.com/forum/#!topic/tortoisesvn/qaJQ_K9Wbb8
The root cause is that GitHub has a non-compliant Subversion Server as described here: https://mail-archives.apache.org/mod_mbox/subversion-users/201811.mbox/%3Cba7c96e5-8a04-e676-9ee7-02357aeb3118%40apache.org%3E
The relevent portions of the above post:
The root cause is that GitHub does not implement Subversion's HTTP/DAV protocol correctly. In 1.11, the Subversion client has become stricter about the server requirements (see: https://svn.apache.org/r1825302). Specifically, we require that the server sends DAV response headers to the OPTIONS request, which we use for capability negotiation. Here's an example of a correct response: HTTP/1.1 200 OK Date: Sun, 04 Nov 2018 15:40:24 GMT Server: Apache/2.4.7 (Ubuntu) DAV: 1,2 DAV: version-control,checkout,working-resource DAV: merge,baseline,activity,version-controlled-collection DAV: http://subversion.tigris.org/xmlns/dav/svn/depth ... The GitHub server does not return any DAV: header for the OPTIONS request, so the response is considered incorrect. I suggest sending a bug report to GitHub; the attached script can be used to simulate Subversion's OPTIONS request. In the meantime, staying with 1.10.x appears to be the only option if you have to use GitHub's SVN protocol.
Is this issue being publically tracked by GitHub Development anywhere? Support’s answer is very generic:
Thanks for writing in to GitHub Support and sorry you have experienced this problem. This error is occurring when using v1.11 of SVN with GitHub. Our engineers are currently working on supporting SVN v1.11. We'll let you know when that support is available. In the meantime you'll need to use an older version in order to connect with GitHub.