> Am 05.11.2018 um 21:57 schrieb Branko Čibej:
>>> Am 05.11.2018 um 20:43 schrieb Stefan Sperling:
>>> On Mon, Nov 05, 2018 at 08:21:20PM -0200, Dr. Rolf Jansen wrote:
>>>> and of course the GitHub server does support HTTP/DAV.
> No it does not. It does not implement the most basic requirements of
> that protocol, which would be to return a response header saying "DAV:
> 1". See https://www.ietf.org/rfc/rfc2518.txt section 15.1.
FYI, RFC 2518 has been obsoleted since 11 years by RFC 4918, and the relevant chapter moved to 10.1: https://tools.ietf.org/html/rfc4918#section-10.1, and yes there is still written "the DAV server MUST return the DAV header". However, the RFC does not require the DAV client to bail out if the server fails to do so, this was your choice.
>>>> # svn co https://github.com/cyclaero/ContentCGI.git/trunk ContentCGI
>>>> svn: E170013: Unable to connect to a repository at URL 'https://github.com/cyclaero/ContentCGI.git/trunk'
>>>> svn: E175003: The server at 'https://github.com/cyclaero/ContentCGI.git/trunk' does not support the HTTP/DAV protocol
>>> There is a problem at Github's end with SVN 1.11.
>>> See the thread titled "Problems accessing GitHub's SVN-bridge with SVN 1.11"
>>> on this very mailing list: https://svn.haxx.se/users/archive-2018-11/0008.shtml
>> In the meantime, I saw this thread.
>>> There is a problem at Github’s end with SVN 1.11.
>> Reading the whole thread, my impression is that there is another issue with the Robustness Principle of software design on Subversion’s end. See: https://en.wikipedia.org/wiki/Robustness_principle.
> We're extremely liberal with that we accept, but it has to at least
> marginally follow the protocol specification.
>> I won’t hold on my breath, until the Subversion Developers and the GitHub engineers sorted out their animosities. I put the patch shown below to /usr/ports/devel/subversion/files/patch-zz-DAV-robustness.local on my FreeBSD system, and then I reinstalled the port - problem solved. Happy discussions!
> Good for you. If you ever get an error saying "Malformed XML in
> response,“ please don't ask us to fix it.
You’ll never find me asking for complex non-solutions to simple non-problems.
Received on 2018-11-06 03:27:56 CET