Skip to content
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

Fix the error message when the token is incorrect (#25701) #25850

Closed

Conversation

GiteaBot
Copy link
Contributor

Backport #25701 by @CaiCandong

we refactored userIDFromToken for the token parsing part into a new function parseToken. parseToken returns the string token from request, and a boolean ok representing whether the token exists or not. So we can distinguish between token non-existence and token inconsistency in the verfity function, thus solving the problem of no proper error message when the token is inconsistent.
close #24439
related #22119

we refactored `userIDFromToken` for the token parsing part into a new
function `parseToken`. `parseToken` returns the string `token` from
request, and a boolean `ok` representing whether the token exists or
not. So we can distinguish between token non-existence and token
inconsistency in the `verfity` function, thus solving the problem of no
proper error message when the token is inconsistent.
close go-gitea#24439  
related go-gitea#22119

---------

Co-authored-by: Jason Song <[email protected]>
Co-authored-by: Giteabot <[email protected]>
@GiteaBot GiteaBot added this to the 1.19.5 milestone Jul 12, 2023
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jul 12, 2023
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 12, 2023
@wolfogre
Copy link
Member

Duplicated with #25834.

Something was going wrong with @GiteaBot.

@wolfogre wolfogre closed this Jul 12, 2023
@GiteaBot GiteaBot removed this from the 1.19.5 milestone Jul 12, 2023
@techknowlogick techknowlogick deleted the backport-25701-v1.19 branch September 9, 2023 05:29
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Oct 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants