-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Since 1.15.0, downloading a release attachment using Basic auth redirect to login #16914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Tried to downgrade to 1.14.6, but, log shows it isn't a good idea:
|
Ah, so we now no longer allow BASIC authentication to get to UI urls. Whilst #15987 added support for raw - no one has reported that releases also need to allow BASIC authentication. A workaround is to use api paths for these. As this change was not intended to be breaking I suspect we should add another PR like #15987. |
Duplicate go-gitea#15987 to allow access to releases download through BASIC authentication. Fix go-gitea#16914 Signed-off-by: Andrew Thornton <art27@cantab.net>
Please could you confirm which urls you need to be able to access through BASIC auth |
All files that are uploaded on a release (we only upload one zip, often named build.zip or dist.zip, but maybe other users upload more files/kind of files), so I think only of: |
go-gitea#16916) Backport go-gitea#16916 Duplicate go-gitea#15987 to allow access to releases download through BASIC authentication. Fix go-gitea#16914 Signed-off-by: Andrew Thornton <art27@cantab.net>
❤️ 1.15.1 deployed, I can confirm this bug is fixed |
[x]
):Description
We used to download release zip (using ansible), since 1.15.0, using curl,
curl --netrc --location https://instance/:owner/:repo/releases/download/:tag/some.zip
redirects to /user/login instead of the attachmentso we have the html page instead of the zip content
Note that getting a file from the repo, for exemple
curl --netrc --location https://instance/:owner/:repo/raw/branch/develop/Jenkinsfile
works well, so definitively not a auth errorDidn't get this issue with 1.14.6 (nor with previous versions)
The text was updated successfully, but these errors were encountered: