Bug report - invalid token results in invalid json

I’m testing my plugin, and when I intentionally send in a bad token, I get bad json back on the websocket.

message out

{
  "message": "register",
  "session_id": "valid session id?",
  "token": "x-bad-token"
}

response

{
  "message": "connection-made"
}

next message

{'re

Please note that this gets sent on a tight loop to syrinscape.

1 Like