Downloads old tar.gz file and on new file got 404 at the webUI #2788

Closed
opened 2025-11-02 04:48:29 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @maxreb on GitHub (Jan 21, 2019).

  • Gitea version (or commit ref): 8a92544 (Current Docker Version)
  • Git version: 2.14.4
  • Operating system: Linux Docker
  • Database (use [x]):
    • PostgreSQL
  • Can you reproduce the bug at https://try.gitea.io:
    • No

Description

I've got a collegue who has created a new git repository on my gitea server. At first everything seemed to work but now everytime he is pushing new commits (with new files) I can't download the files but got a 404 on the webUI. When I try to download the .tar.gz or zip file of the current repository the only files included are the files from the first commit. It is a public repository and I am an employee of that repository. The URL is e.g.:
https://git.myserver.com/My.Collegue/esz/src/branch/refs/remotes/origin/master/frozen_inference_graph_100k.pb

git clone or git pull works like a charme and does not make any problems.

Yes, I am behind a reverse proxy (nginx) but even if I try to connect directly (docker localhost) I've run into the same problem

Screenshots

image

Originally created by @maxreb on GitHub (Jan 21, 2019). - Gitea version (or commit ref): 8a92544 (Current Docker Version) - Git version: 2.14.4 - Operating system: Linux Docker - Database (use `[x]`): - [x] PostgreSQL - Can you reproduce the bug at https://try.gitea.io: - [x] No ## Description I've got a collegue who has created a new git repository on my gitea server. At first everything seemed to work but now everytime he is pushing new commits (with new files) I can't download the files but got a 404 on the webUI. When I try to download the .tar.gz or zip file of the current repository the only files included are the files from the first commit. It is a public repository and I am an employee of that repository. The URL is e.g.: `https://git.myserver.com/My.Collegue/esz/src/branch/refs/remotes/origin/master/frozen_inference_graph_100k.pb` `git clone` or `git pull` works like a charme and does not make any problems. Yes, I am behind a reverse proxy (nginx) but even if I try to connect directly (docker localhost) I've run into the same problem ## Screenshots ![image](https://user-images.githubusercontent.com/39700092/51479387-5deebf80-1d8e-11e9-84d5-ec86b30a61da.png)
GiteaMirror added the issue/needs-feedback label 2025-11-02 04:48:29 -06:00
Author
Owner

@lafriks commented on GitHub (Jan 21, 2019):

Can not seem to reproduce that, can you reproduce this problem in https://try.gitea.io/?

@lafriks commented on GitHub (Jan 21, 2019): Can not seem to reproduce that, can you reproduce this problem in https://try.gitea.io/?
Author
Owner

@maxreb commented on GitHub (Jan 22, 2019):

No i can not. My user is the administrator, the other user is just a user.

@maxreb commented on GitHub (Jan 22, 2019): No i can not. My user is the administrator, the other user is just a user.
Author
Owner

@lafriks commented on GitHub (Jan 22, 2019):

I tried both behind reverse proxy and directly and can not reproduce it both using admin user or normal

@lafriks commented on GitHub (Jan 22, 2019): I tried both behind reverse proxy and directly and can not reproduce it both using admin user or normal
Author
Owner

@zeripath commented on GitHub (Jan 22, 2019):

@maxreb Do you have ENABLE_GZIP set by any chance?

@zeripath commented on GitHub (Jan 22, 2019): @maxreb Do you have ENABLE_GZIP set by any chance?
Author
Owner

@maxreb commented on GitHub (Jan 23, 2019):

@maxreb Do you have ENABLE_GZIP set by any chance?

@zeripath I don't have that enabled in my app.ini.

I can't reproduce it either with the actual version (8a92544). It seems that while one commit/push something went corrupt. If noone has any idea what could have triggered this phenomen, I think we can close this issue and I'll ask my collegue to reupload the whole thing in a new repository.

@maxreb commented on GitHub (Jan 23, 2019): > @maxreb Do you have ENABLE_GZIP set by any chance? @zeripath I don't have that enabled in my `app.ini`. I can't reproduce it either with the actual version (8a92544). It seems that while one commit/push something went corrupt. If noone has any idea what could have triggered this phenomen, I think we can close this issue and I'll ask my collegue to reupload the whole thing in a new repository.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2788