[ 
https://issues.apache.org/jira/browse/SVN-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Branko Čibej updated SVN-4789:
------------------------------
    Description: 
TL;DR: GitHub's Subversion bridge does not return the required "{{DAV:}}" 
header in responses, so the Subversion client from 1.11.0 onwards refuses to 
connect to it.

See [this mail 
thread|https://lists.apache.org/thread.html/90c028421ac86f787c2101ab61a70ec5fa0a6f4d617a8b87be802e5c@%3Cusers.subversion.apache.org%3E]
 on users@.
Also see [this mail 
thread|https://lists.apache.org/thread.html/5254c3eaa06c194e6e2a9d22f976a4c65dde98c95a1c1af606d81e3e@%3Cdev.subversion.apache.org%3E]
 on dev@.

  was:
TL;DR: GitHub's Subversion bridge does not return the required "{{DAV:}}" 
header in responses, so the Subversion client from 1.11.0 onwards refuses to 
connect to it.

See [this mail 
thread|https://lists.apache.org/thread.html/90c028421ac86f787c2101ab61a70ec5fa0a6f4d617a8b87be802e5c@%3Cusers.subversion.apache.org%3E]
 on users@.



> Support GitHub's broken Subversion bridge
> -----------------------------------------
>
>                 Key: SVN-4789
>                 URL: https://issues.apache.org/jira/browse/SVN-4789
>             Project: Subversion
>          Issue Type: New Feature
>          Components: libsvn_ra_serf
>    Affects Versions: 1.11.0
>            Reporter: Branko Čibej
>            Assignee: Branko Čibej
>            Priority: Major
>         Attachments: github-request-id.patch
>
>
> TL;DR: GitHub's Subversion bridge does not return the required "{{DAV:}}" 
> header in responses, so the Subversion client from 1.11.0 onwards refuses to 
> connect to it.
> See [this mail 
> thread|https://lists.apache.org/thread.html/90c028421ac86f787c2101ab61a70ec5fa0a6f4d617a8b87be802e5c@%3Cusers.subversion.apache.org%3E]
>  on users@.
> Also see [this mail 
> thread|https://lists.apache.org/thread.html/5254c3eaa06c194e6e2a9d22f976a4c65dde98c95a1c1af606d81e3e@%3Cdev.subversion.apache.org%3E]
>  on dev@.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to