Skip to content

Answer 503, not 401, when a session code's keys could not be read #116

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.

Sign up for GitHub

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

Merged
feruzm merged 3 commits into from
Nov 8, 2026
Merged

Answer 503, not 401, when a session code's keys could not be read #116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e518e93
Answer 503, not 401, when a session code's keys could not be read
feruzm Nov 8, 2026
b6e9264
Bound stale HiveSigner keys, treat unusable key lists and post-refres…
feruzm Nov 8, 2026
e25bc4b
Refuse non-account names before the read; any failed read, RPC errors…
feruzm Nov 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,3 +127,10 @@ without a type.
Handlers using `RequireAuthedUsername` differ from those calling `ValidateCode`
directly only in that the former sends the 401 for you - the validation is the
same, so it is never the explanation for one route failing while another passes.

A 401 from `ValidateCode` is always a verdict from the chain's answer (no such
account, a key that does not match, a malformed or non-session code). When the
keys could not be read at all (node error, timeout, an unusable answer), it
throws `TokenCheckUnavailableException` and `ServerErrors` answers 503
"Service Unavailable" with `Retry-After`, so clients do not take a node outage
for a refused session. Do not catch that exception in a handler.
Loading
Loading