Details
-
Bug
-
Resolution: Fixed
-
Medium
Description
There seems to be a problem with https authentication. The problem occurs when cloning my private repository. It basically seems to boil down to this
- git makes a GET request via curl
- bitbucket.org responds with 401 unauthorized and a WWW-Authenticate header field
- git makes a second GET request with proper Authorization header set
- bitbucket.org responds with 200 OK (and empty content?)
- git makes a POST git-upload-pack request
- bitbucket.org again responds with 401 header and WWW-Authenticate header field
- git exits with error: RPC failed; result=22, HTTP code = 401
full log (stripped of sensitive information) is attached