500 Internal Server Error when accessing nonexistent commit #5136

New Issue

GiteaMirror · 2025-11-02T06:15:34-06:00

GiteaMirror commented

2025-11-02 06:15:34 -06:00

Originally created by @tobiaswiese on GitHub (Mar 27, 2020).

Gitea version (or commit ref): 1.11.3
Git version: 2.20.1
Operating system: Debian Buster
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes: aa64449a8c
- No
- Not relevant
Log gist: Not relevant

Description

When accessing a commit that doesn't exist (either by typing nonsense into the url bar, or because it was later cleaned up by the garbage collector), the server fails with a 500 error, insead of a 404.

Screenshots

https://try.gitea.io/img/500.png

Originally created by @tobiaswiese on GitHub (Mar 27, 2020).   - Gitea version (or commit ref): 1.11.3 - Git version: 2.20.1 - Operating system: Debian Buster - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: https://try.gitea.io/go-gitea/blog/commit/aa64449a8c91c7057c89322881794caf15590eb3 - [ ] No - [ ] Not relevant - Log gist: Not relevant ## Description When accessing a commit that doesn't exist (either by typing nonsense into the url bar, or because it was later cleaned up by the garbage collector), the server fails with a 500 error, insead of a 404. ## Screenshots https://try.gitea.io/img/500.png

GiteaMirror added the type/bug label 2025-11-02 06:15:34 -06:00

GiteaMirror closed this issue

2025-11-02 06:15:35 -06:00

GiteaMirror commented

2025-11-02 06:15:36 -06:00

@lunny commented on GitHub (Mar 27, 2020):

This may has been fixed by @zeripath .

@lunny commented on GitHub (Mar 27, 2020): This may has been fixed by @zeripath .

GiteaMirror commented

2025-11-02 06:15:36 -06:00

@zeripath commented on GitHub (Mar 28, 2020):

Nope I hadn't fixed this one - but it needs a similar fix to the other places.