API raw route should support tags/branches

[brandonkal]

• Gitea version (or commit ref): master

Description

/repos/{owner}/{repo}/raw/{filepath} only supports the master branch. It should also support specifying branch and tag.

As far as I can tell, I have to use the /repos/{owner}/{repo}/contents/{filepath} route and then decode the base64 contents.

For my specific use case, I would also like to see the raw download url accept Authorization token headers.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[zeripath]

Why can't you use the ?ref= parameter.

[neolithos]

Because is not mentioned in the swagger help page.

[zeripath]

Actually I'm wrong the ref Param isn't used on this path. Apologies.

However looking at the code, I think the file path needs to be the same as on the actual site.

That is:

/api/v1/repos/{owner}/{name}/raw/branch/{branch name}/{file path}

And so on for tags and commits

[d-lunyov]

Looks like it is duplicate #14597