eliets2 a0180da9b6 Reply to non-UTF8 lines on the control channel (#118) ...

Clients cannot tell a refused non-UTF8 request from a dropped connection, unlike malformed JSON which gets an explicit error reply.

Make the TCP control servers reply with an error for non-UTF8 lines, closing before auth and continuing after auth like bad JSON.

Test: non_utf8_line_before_auth_gets_refusal_reply failed before the change and passes after.

Co-authored-by: eliets2 <287273517+eliets2@users.noreply.github.com>
Co-authored-by: FredApps <153173854+FredApps@users.noreply.github.com>

2026-11-06 10:10:38 +01:00

..

materialcraft

Reply to non-UTF8 lines on the control channel (#118)

2026-11-06 10:10:38 +01:00

materialcraft-cli

Merge main while preserving native graph architecture

2026-11-06 00:58:56 -05:00

materialcraft-web

Start desktop and browser sessions with an empty graph (#29)

2026-11-04 06:17:40 +01:00