404 for API request against /user/{username}/orgs #2631

New Issue

GiteaMirror · 2025-11-02T04:42:50-06:00

GiteaMirror commented

2025-11-02 04:42:50 -06:00

Originally created by @ChriFo on GitHub (Dec 6, 2018).

Gitea version (or commit ref): 328e38e built with: bindata, sqlite
Git version: 2.15.3
Operating system: Docker/Alpine
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

An GET request against https://try.gitea.io/api/v1/user/krischan157/orgs should return one organization called tree. But the response is an HTTP 404.

The GET request against https://try.gitea.io/api/v1/user/orgs is correctly returning the tree organization.

For both requests the user krischan157 was used for authorization.

Originally created by @ChriFo on GitHub (Dec 6, 2018). - Gitea version (or commit ref): 328e38e built with: bindata, sqlite - Git version: 2.15.3 - Operating system: Docker/Alpine - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant ## Description An GET request against https://try.gitea.io/api/v1/user/krischan157/orgs should return one organization called _tree_. But the response is an HTTP 404. The GET request against https://try.gitea.io/api/v1/user/orgs is correctly returning the tree organization. For both requests the user krischan157 was used for authorization.

GiteaMirror closed this issue

2025-11-02 04:42:50 -06:00

GiteaMirror commented

2025-11-02 04:42:51 -06:00

@lunny commented on GitHub (Dec 8, 2018):

You should visit https://try.gitea.io/api/v1/users/krischan157/orgs but not https://try.gitea.io/api/v1/user/krischan157/orgs

@lunny commented on GitHub (Dec 8, 2018): You should visit `https://try.gitea.io/api/v1/users/krischan157/orgs` but not `https://try.gitea.io/api/v1/user/krischan157/orgs`

GiteaMirror commented

2025-11-02 04:42:51 -06:00

@ChriFo commented on GitHub (Dec 8, 2018):

@lunny Thanks. You are right. But the request against https://try.gitea.io/api/v1/users/krischan157/orgs ist empty, too. Response code ist 200.

@ChriFo commented on GitHub (Dec 8, 2018): @lunny Thanks. You are right. But the request against https://try.gitea.io/api/v1/users/krischan157/orgs ist empty, too. Response code ist 200.

GiteaMirror commented

2025-11-02 04:42:51 -06:00

@lunny commented on GitHub (Dec 8, 2018):

Because krischan157 is a private user of the org tree, so he's org will not be shown. And I have allowed admin to see that on PR #5494

@lunny commented on GitHub (Dec 8, 2018): Because krischan157 is a private user of the org `tree`, so he's org will not be shown. And I have allowed admin to see that on PR #5494

GiteaMirror referenced this issue

2025-11-02 16:04:19 -06:00

[PR #5522] [MERGED] fix detect force push failure on deletion of protected branches #17826

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#2631