randogoth/smolmail
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: specify client handling of unassigned status codes

Browse source
This commit is contained in:
randogoth 2026-09-27 18:09:26 +03:00
parent 9ab5b0f401
commit fa20ac1034
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
SPEC.md
View file

@ -391,4 +391,4 @@ Abuse control is quotas, size caps and rate limits: per-IP connection and `SEND`
2 bad version 5 auth failed 8 rate limited 2 bad version 5 auth failed 8 rate limited
``` ```
A status is the first byte of every response body (§6.1), which MAY be followed by a UTF-8 reason string. Clients MUST NOT parse the reason. A status is the first byte of every response body (§6.1), which MAY be followed by a UTF-8 reason string. Clients MUST NOT parse the reason. Codes not listed are unassigned: a client MUST treat one it does not know as a failure of the operation, MUST NOT retry automatically, and SHOULD surface the number.