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

Re: subversion 1.11.0 on FreeBSD 11.2: ... does not support the HTTP/DAV protocol

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 06 Nov 2018 03:57:19 +0000

Dr. Rolf Jansen wrote on Tue, 06 Nov 2018 00:27 -0200:
> 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.

There are two schools of thought: one, "be strict in what you send and
lenient in what you accept"; two, "be strict in what you send and strict
in what you accept". This list is not a good place to have
a discussion about which one is better in general. Instead, let's focus on
the specific problem at hand. If you have an idea for how we might continue
operating with GitHub without regressing the failure mode that that error
message was added to fix, we're all ears.

The obvious idea is to wait a few days for GitHub to make the one-line
change to their server code which will fix the issue.


Received on 2018-11-06 04:57:32 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.