Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Download Release Attachment via API #18702

Open
noetzold opened this issue Feb 10, 2022 · 5 comments
Open

Download Release Attachment via API #18702

noetzold opened this issue Feb 10, 2022 · 5 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@noetzold
Copy link

Feature Description

When using the API to download release attachment via /repos/{owner}/{repo}/releases/{id}/assets/{attachment_id} a download link is provided. But downloading requires login. So, the use of this API call is verry limited. Is would be nice to have a way downloading the attachment with an access token.

Screenshots

No response
@6543
Copy link
Member

6543 commented Feb 10, 2022

https://try.gitea.io/api/swagger#/repository/repoGetReleaseAttachment

@6543 6543 added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Feb 10, 2022
@noetzold
Copy link
Author

noetzold commented Feb 10, 2022 •
edited
Loading

Yes, this is the API call returning a “browser_download_url”
For example:
https://try.gitea.io/api/v1/repos/fnetx/testing-gitea-releases/releases/3318489/assets/2114?access_token=12345
"browser_download_url": "https://try.gitea.io/attachments/f505c259-0ccf-4b66-893d-1f4880f236aa"

But when using authorization a login with user/password is required for downloading the file.

@6543 6543 added type/proposal The new feature has not been accepted yet but needs to be discussed first. and removed issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Feb 10, 2022
@6543
Copy link
Member

6543 commented Feb 10, 2022

well either add token auth to this endpoint or add a new endpoint ...

@ajtuma
Copy link

ajtuma commented Aug 22, 2023

A new endpoint... Could you please explain it more widely?

@lunny
Copy link
Member

lunny commented Aug 22, 2023

#26430 should fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @6543 @noetzold @ajtuma