After a couple round-trip connection closes with Protocol Error

Jul 23, 2014 at 4:55 AM
Hi!

I'm using SuperWebSocket on a console application to host my server, I'm connecting with chrome.

My server starts sending a "LOGIN" message.
The client open up a form for the user to login, if the user clicks on sign up, it sends a "SignUp" message, and receives a "SignUp <guid>" message back with a guid.
At this moment if I click cancel and click sign up again (to send another "SIGNUP" message to the server, I'm expecting to get another "SIGNUP <guid>" message back, but instead I'm getting a protocol error and losing my connection.

No message on the error log, only a message on DEBUG saying a protocol error occurred.

Can anyone help me?

Thanks!
Jul 23, 2014 at 5:05 AM
On my tests I found out that the second time I call send from my webpage, it doesn't matter what text I'm sending or if I got a response or not, my connection will break with Protocol Error.
Coordinator
Aug 9, 2014 at 6:15 AM
Did you check the error log?
Aug 9, 2014 at 9:09 PM
Yes I did, as I mention on my original post:
"No message on the error log, only a message on DEBUG saying a protocol error occurred. "