Currently if connection_init fails and then a start message arrives, the error is start received before the connection is initialized. The error should instead by cannot start as connection_init failed: <connection_init error message>.

This happens when the client does not check for the response from the server after connection_init and blindly sends start message (graphiql seems to be doing this).