nats.go
nats.go copied to clipboard
Parser accepts inlined status directly after `NATS/1.0`
Currently, a message with headers in this form is accepted, and the (incorrectly?) inlined status 418
is read:
NATS/1.0418
Example: test
This seems like a bug in the parser.
I would expect ErrBadHeaderMsg
to be returned from decodeHeadersMsg
.
Instead, the call succeeds (with the Status
header set to 418
).