Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Received a strange error when using secure websockets in Safari with Webbit server.
Error during WebSocket handshake: location mismatch: wss://domain.com:5679/ != ws://domain.com:5679/
I have no idea why this would happen or how to get around it. Is this a bug on the Webbit server or a client-side bug?
Confirmed it was a bug. Glad to report that this was fixed in both the Hixie 75 and 76 protocol specs in Webbit via this pull request https://github.com/webbit/webbit/pull/84
If you are using any other websocket libraries other than Webbit, I suggest tracking down the source and looking for where the protocol is determined when responding to a secure websocket request.