-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send 404 on /{org}.gpg
#18959
Send 404 on /{org}.gpg
#18959
Conversation
Gusted
commented
Mar 1, 2022
- Organizations currently cannot have any GPG/SSH keys, so send 404 status instead of a internal server error.
- Resolves 500 on organization.gpg request #18952
- Organisation's currently cannot have any GPG/SSH keys, so send 404 status instead of a internal server error. - Resolves go-gitea#18952
Accidently fixed in #18798 too. In that case an invalid response is generated. I think there should be an |
Yeah it should be, as it shouldn't send invalid keys... Does it bother your PR if that's also fixed in this PR? Otherwise I will give a look over your PR and close this one. |
The problem is the indirect User->Org redirect in |
I added another PR for the invalid response: #18961 |
* giteaofficial/main: Send 404 on `/{org}.gpg` (go-gitea#18959) Accounts with WebAuthn only (no TOTP) now exist ... fix code to handle that case (go-gitea#18897) Fix lfs management setting (go-gitea#18946) Fix admin user list pagination (go-gitea#18957)