New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket.io can't connect to WebSockets (only) #1208
Comments
@patrickbussmann actually, Socket.IO is not a WebSocket implementation, it has its own protocol which may use a WebSocket connection to transmit data. |
But i think When i specify it in the options it should use only websockets.
Do you know how to use Ratchet PHP with Socket.IO?
It Supports http Server etc also.
But tested and not works.
|
@patrickbussmann Brother, I also encountered this problem, I want to find a websocket tool,but this seems to be used only Socket.io as server side.Have you found a solution? |
Hi @hongweipeng, |
@patrickbussmann Well,Im also going to use the same way as you, thx. |
emmm socket.io-client connected java websocket, but don't know how to exchange message |
For future readers, please see https://socket.io/docs/v3/#What-Socket-IO-is-not |
You want to:
Current behaviour
I connect to a WebSocket using Socket.io and no connection will be established.
The WebSocket server (PHP Ratchet) detects a connection but this will be closed soon and Socket.IO never says that the client is connected to the server.
Steps to reproduce (if the current behaviour is a bug)
Error:
Error during WebSocket handshake: Unexpected response code: 403
This is working:
-> Tested in the console of https://socket.io/get-started/chat/ <-
Expected behaviour
That socket.io can handle the WebSocket 👍
Setup
The text was updated successfully, but these errors were encountered: