Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Websocket service user authentication #73
Yes. Theoretically you could use HTTP basic auth, but I wouldn't recommend it. The WebSocket specification does not include any kind of authentication mechanism. It is left to the individual protocol designer to decide how best to perform authentication in their application.
The simplest thing to do might be to send the credentials from the client as the first message after the connection is successful, and then send back a response from the server, additionally closing the connection if the authentication failed. Obviously the server shouldn't process any other kind of messages until the authentication phase is complete.
Sent from my iPhone
On Jan 6, 2013, at 2:17 PM, Andrew Faulds firstname.lastname@example.org wrote: