-
Bug
-
Resolution: Fixed
-
Low
-
2.0.1
-
None
A reported a problem with cloning repositories via HTTP with recent versions of Git.
Either due to a change in git or a particular version of libcurl git was compiled against the Not Authenticated String Stash sends back to the client causes git to not identify the repository as supporting the smart HTTP protocol.
Symptoms: a clone attempt aborts with
fatal: http://user@example.com:7990/scm/PROJECT/repo.git/info/refs not valid: is this a git repository?
To workaround this problem, Stash should supply an empty response body when returning a 401 to the git client.
- relates to
-
BSERV-4426 Document known compatibility matrix for building git from source
- Closed
[BSERV-2966] Shouldn't supply a response body to Git clients when returning 401 response
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 122850 ] |
Workflow | Original: Stash Workflow - Restricted [ 1447189 ] | New: JAC Bug Workflow v3 [ 3136060 ] |
Workflow | Original: Stash Workflow [ 455906 ] | New: Stash Workflow - Restricted [ 1447189 ] |
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 122850 ] | New: This issue links to "Page (Atlassian Documentation)" [ 122850 ] |
Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 122850 ] |
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 115916 ] | New: This issue links to "Page (Atlassian Documentation)" [ 115916 ] |
Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 115916 ] |
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 115538 ] | New: This issue links to "Page (Atlassian Documentation)" [ 115538 ] |
Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 115538 ] |
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 107554 ] | New: This issue links to "Page (Atlassian Documentation)" [ 107554 ] |