Details
-
Bug
-
Resolution: Fixed
-
High
Description
I have an application that uses a user's OAuth credentials to download the contents of a repository as a tarball at a particular commit id.
According to my logs, everything was working well on 2016-02-04, and broke overnight into 2016-02-05.
The requests look like:
$ curl -i https://x-token-auth:ACCESS_TOKEN@bitbucket.org/OWNER/REPO/get/master.tar.gz HTTP/1.1 401 UNAUTHORIZED Server: nginx/1.6.2 Vary: Accept-Language, Cookie WWW-Authenticate: Basic realm="Bitbucket.org HTTP" Content-Type: text/html; charset=utf-8 Strict-Transport-Security: max-age=31536000 Date: Fri, 05 Feb 2016 18:32:12 GMT X-Served-By: app12 Content-Language: en X-Static-Version: 93ed08e24088 ETag: "d41d8cd98f00b204e9800998ecf8427e" X-Render-Time: 0.0259521007538 Connection: keep-alive X-Version: 93ed08e24088 X-Request-Count: 427 X-Frame-Options: SAMEORIGIN Content-Length: 0
If I use the same credentials to perform a clone, it works perfectly:
$ git clone https://x-token-auth:ACCESS_TOKEN@bitbucket.org/OWNER/REPO.git
Cloning into 'REPO'...
remote: Counting objects: 375, done.
remote: Compressing objects: 100% (201/201), done.
remote: Total 375 (delta 211), reused 285 (delta 163)
Receiving objects: 100% (375/375), 30.32 KiB | 0 bytes/s, done.
Resolving deltas: 100% (211/211), done.
Checking connectivity... done.
However, opening the download link in my authenticated browser session works and downloads the repository.
So is this a bug that's still intended to work, or will has this method of downloading the repository via API discontinued?
My application is currently broken for Bitbucket users as a result, and I need to know one way or another to keep or replace the functionality.