[API] GET /repos/{owner}/{repo}/contents/{filepath} returns null content on big files #6737

New Issue

GiteaMirror · 2025-11-02T07:05:05-06:00

GiteaMirror commented

2025-11-02 07:05:05 -06:00

Originally created by @danielemoroni on GitHub (Jan 22, 2021).

Gitea version (or commit ref): 1.12.3 and 1.14.0+dev-587-g61f9a72f2
Git version:
Operating system:
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (https://try.gitea.io/danielemoroni/bigfile_test)
- No
Log gist:

Description

I uploaded a 14MB file to a repository, and tried the API GET /repos/{owner}/{repo}/contents/{filepath}. Example in try.gitea.io swagger: curl -X GET "https://try.gitea.io/api/v1/repos/danielemoroni/bigfile_test/contents/bigfile.dat" -H "accept: application/json"

I get a response 200 but the content is empty. It's fine if I use the raw api instead, GET /repos/{owner}/{repo}/raw/{filepath}.

Is this a known limit in gitea? I couldn't find any documentation or issue about it.

Screenshots

Originally created by @danielemoroni on GitHub (Jan 22, 2021).   - Gitea version (or commit ref): 1.12.3 and 1.14.0+dev-587-g61f9a72f2 - Git version: - Operating system:    - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/danielemoroni/bigfile_test) - [ ] No - Log gist:    ## Description I uploaded a 14MB file to a repository, and tried the API GET /repos/{owner}/{repo}/contents/{filepath}. Example in try.gitea.io swagger: curl -X GET "https://try.gitea.io/api/v1/repos/danielemoroni/bigfile_test/contents/bigfile.dat" -H "accept: application/json" I get a response 200 but the content is empty. It's fine if I use the raw api instead, GET /repos/{owner}/{repo}/raw/{filepath}. Is this a known limit in gitea? I couldn't find any documentation or issue about it. ## Screenshots

GiteaMirror added the issue/needs-feedback type/bug modifies/api labels 2025-11-02 07:05:05 -06:00

GiteaMirror closed this issue

2025-11-02 07:05:05 -06:00

GiteaMirror commented

2025-11-02 07:05:06 -06:00

@lunny commented on GitHub (Jan 25, 2021):

~~It's OK from me.~~

@lunny commented on GitHub (Jan 25, 2021): ~It's OK from me.~ ![image](https://user-images.githubusercontent.com/81045/105663451-38f92e00-5f0d-11eb-9f11-a937b9286823.png)

GiteaMirror commented

2025-11-02 07:05:06 -06:00

@danielemoroni commented on GitHub (Jan 26, 2021):

The response is ok, but content is empty. It's at the end of the first line in your screenshot: "content": ""

For smaller files that field is populated with the file content (as a base64 string).

Incidentally the limit seems to be around 10MB, as I can get a 9.6MB file ok.

@danielemoroni commented on GitHub (Jan 26, 2021): The response is ok, but content is empty. It's at the end of the first line in your screenshot: "content": "" For smaller files that field is populated with the file content (as a base64 string). Incidentally the limit seems to be around 10MB, as I can get a 9.6MB file ok.

GiteaMirror commented

2025-11-02 07:05:06 -06:00

@6543 commented on GitHub (Jan 26, 2021):

I think this is because to convert it into json the whole file is first loaed into mem and then encoded ... to solve this It looks like we have to stream encode it ...?

@6543 commented on GitHub (Jan 26, 2021): I think this is because to convert it into json the whole file is first loaed into mem and then encoded ... to solve this It looks like we have to stream encode it ...?

GiteaMirror commented

2025-11-02 07:05:07 -06:00

@wxiaoguang commented on GitHub (Jun 23, 2025):

Could you try 1.24 or main nightly? I think the problem should have been fixed for large files.

Now the response should never be null, only "Encoding" and "Content" fields will be null for large files.

@wxiaoguang commented on GitHub (Jun 23, 2025): Could you try 1.24 or main nightly? I think the problem should have been fixed for large files. Now the response should never be null, only "Encoding" and "Content" fields will be null for large files.

GiteaMirror commented

2025-11-02 07:05:07 -06:00

@GiteaBot commented on GitHub (Jul 24, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jul 24, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6737

[API] GET ​/repos​/{owner}​/{repo}​/contents​/{filepath} returns null content on big files #6737

Description

Screenshots

[API] GET /repos/{owner}/{repo}/contents/{filepath} returns null content on big files #6737