mirror of
https://gitea.com/gitea/tea.git
synced 2026-09-15 18:06:19 -04:00
9bd537c72e
The custom api client only sent a bearer token, so a login that authenticates with an SSH key (HTTP Signature) sent no credentials at all — `tea api` failed with 401/404 on every endpoint. The SDK signs such requests; the custom client did not. Authenticate via token or SSH key/cert, reusing the SDK's exported HTTPSign signer construction plus the same httpsig signing path. Also detect MSYS2/Git-Bash path mangling of the endpoint argument and surface a clear, actionable error instead of a confusing "404 page not found". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| auth | ||
| config | ||
| context | ||
| debug | ||
| filelock | ||
| git | ||
| httputil | ||
| interact | ||
| task | ||
| theme | ||
| utils | ||
| version | ||