On 04.11.2018 20:11, Branko Čibej wrote: > On 04.11.2018 18:57, Thorsten Schöning wrote: >> Guten Tag Branko Čibej, >> am Sonntag, 4. November 2018 um 17:47 schrieben Sie: >> >>> I'm not sure what you mean by "handles more than only DAV successfully" >> I thought it might be possible that GitHub answers differently but >> properly, because the other check mentioned something about HTTP v2. >> Because of TLS, I was unable to look at the requests and responses >> then, but it's like you said, they don't provide DAV-headers in their >> response to OPTION. >> >>> And yes, the HTTP/DAV specification requires that header to be present >>> in the response. >> Which you didn't care about before and things worked for some years >> for some users. > We made this change because users complained about unhelpful error > messages when they tried to connect to a server that did not even > implement HTTP/DAV. The error message was "Malformed XML in response" > which wasn't exactly helpful for diagnosing the problem. > > I admit I didn't have GitHub in mind when I added this check. ...
I added a test case to our suite that tries the following command: svn info https://github.com/apache/subversion/trunk It runs on one of our build slaves, so we'll know fairly soon when (if) GitHub deploys a fix. And, of course, we'll also know if this feature breaks again in future. http://svn.apache.org/r1845942 -- Brane