You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.