menuTicketing

E · Error

Structure
Example refresh

An invalid request. Instead of a key, a reason (reason) text is included.

reasoncauseafterward
bad_opunknown opconnection kept alive
bad_keykey missing / exceeds 128B / contains whitespace or newline / not UTF-8connection kept alive
bad_ttllease = 0connection kept alive
bad_requestA fixed fields (4B) insufficientconnection kept alive
line_too_longexceeds 192Bconnection kept alive (re-synchronizes at the next \n)
not_activerequest sent to a standbyconnection closed after the response

line_too_long does not close the connection — even if the client accidentally sends an overly long frame, the socket stays open and framing naturally re-synchronizes at the next \n.

Byte notation: op is an ASCII character, and reason is ASCII text (variable-length, shown as N in the structure). The trailing \n is 0A.