Problem with client reconnection #113
Description
Hitting on a peculiar problem. A web browser client is broken due to network issues, and then tries to reconnect again once network is back. The server continues to think the connection is alive, and so dumps the HTTP request headers as the next WebSocket message received.