From the Socket.IO README:
Note: Socket.IO is not a WebSocket implementation. Although Socket.IO indeed uses WebSocket as a transport when possible, it adds some metadata to each packet: the packet type, the namespace and the ack id when a message acknowledgement is needed. That is why a WebSocket client will not be able to successfully connect to a Socket.IO server, and a Socket.IO client will not be able to connect to a WebSocket server (like ws://echo.websocket.org) either. Please see the protocol specification here.
Channels doesn’t support socket.io – it’s a different protocol that isn’t websockets or HTTP but layers on top of them. You’ll have to use a socket.io server if you want to use it.
- How to return data with 403 error in Django Rest Framework?
- UnicodeEncodeError：'latin-1' codec can't encode characters in position 0-1: ordinal not in range(256)
- How to disable request logging in Django and uWSGI?