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

Re: Problems accessing GitHub's SVN-bridge with SVN 1.11

From: Daniel Shahaf <danielsh_at_apache.org>
Date: Sun, 4 Nov 2018 16:02:38 +0000

Thorsten Schning wrote on Sun, Nov 04, 2018 at 16:42:11 +0100:
> Guten Tag Thorsten Schning,
> am Sonntag, 4. November 2018 um 16:05 schrieben Sie:
> >> The server at '[...]' does not support the HTTP/DAV protocol.
> Others have the same problem and while it is true that GitHub might
> have implemented something on their own, it might help to have a look
> at the changes between 1.10 and 1.11 regarding the protocol.

That took exactly two minutes to grep, diff, and blame.

See https://svn.apache.org/r1825302. 1.11 has new behaviour whereby it
deliberately errors out if the HTTP response does not include a "DAV:"
header, apparently in to improve the failure mode on URLs that are not
Subversion repository URLs.

> I've already written to the GitHub support but nobody seemed to care yet.

Well, we can't fix this issue on our end. Our client code works with
our server code, but there is no way for us to ensure that our client
code (continues to) work with third-party server reimplementations.
That said, if any GitHub staff are reading this, you're welcome to
contact us on the dev@ list and we'll see what we can do.


(We can't just "remove the new check" because that would regress the
failure mode that check was added to improve.)
Received on 2018-11-04 17:02:56 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.