wget on repository tag returning 404

[aaron.mchugh]

I'm trying to deploy code to our staging environment as usual and the download file for the version is returning 404. I have seen the other posts around updating GoLang but I can't see anywhere in the project where we use GoLang.

Thanks for any help.

[Theodora Boudale · Accepted solution]

Hi @aaron.mchugh and welcome to the community!

We have recently made a change where we return 404 instead of 403 code for unauthenticated users, which has caused an issue in downloading the archive from Bitbucket using wget.

The wget command always waits for the 403 challenge from the server before it sends the credentials to the server.
However, with the recent changes, our server initially sends the 404 status to the client and wget doesn't send credentials later on.

We have two suggestions to work around this issue:

1. You can use the --auth-no-challenge flag in the wget command as follows:

wget --user=BitbucketUsername --password=AppPassword --auth-no-challenge https://bitbucket.org/Workspace-ID/Repo/get/master.tar.gz

2. Alternatively, you can download the file using curl:

curl -u BitbucketUsername:AppPassword https://bitbucket.org/Workspace-ID/Repo/master.tar.gz -o master.tar.gz

Kind regards,
Theodora