4 people 353dcc5ad4 Fix the error message when the token is incorrect (#25701) (#25836) ...

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

Co-authored-by: caicandong <[email protected]>
Co-authored-by: Jason Song <[email protected]>

2023-07-12 10:18:27 +00:00

..

e2e

Rewrite logger system (#24726)

2023-05-21 22:35:11 +00:00

fuzz

Move fuzz tests into tests/fuzz (#22376)

2023-01-09 15:30:14 +08:00

gitea-lfs-meta

Test views of LFS files (#22196)

2022-12-23 07:41:56 +08:00

gitea-repositories-meta

Fix bug of branches API with tests(#25578) (#25579)

2023-07-03 16:17:30 +02:00

integration

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

2023-07-12 10:18:27 +00:00

mssql.ini.tmpl

Implement actions artifacts (#22738)

2023-05-19 21:37:57 +08:00

mysql8.ini.tmpl

Implement actions artifacts (#22738)

2023-05-19 21:37:57 +08:00

mysql.ini.tmpl

Implement actions artifacts (#22738)

2023-05-19 21:37:57 +08:00

pgsql.ini.tmpl

Implement actions artifacts (#22738)

2023-05-19 21:37:57 +08:00

sqlite.ini.tmpl

Implement actions artifacts (#22738)

2023-05-19 21:37:57 +08:00

test_utils.go

Replace interface{} with any (#25686) (#25687)

2023-07-04 23:41:32 -04:00