[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: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Sun, 4 Nov 2018 18:57:10 +0100

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. Now "we" need to get GitHub to change their
implementation and I didn't even get an automatic bot-reply to my
question on Friday yet. :-) Lets see how things are going after I send
them this thread...

Thank you both for your time anyway!

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2018-11-04 18:57:20 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.