Difference between revisions of "Socket.io-client"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 13: | Line 13: | ||
socket.io-parser decoded 4{"message":"No auth token"} as {"type":4,"nsp":"/","data":{"message":"[[No auth token]]"}} +732ms | socket.io-parser decoded 4{"message":"No auth token"} as {"type":4,"nsp":"/","data":{"message":"[[No auth token]]"}} +732ms | ||
| − | + | == See also == | |
* {{socket}} | * {{socket}} | ||
Revision as of 06:28, 14 March 2023
As explained in the "What Socket.IO is not" section, the Socket.IO client is not a WebSocket implementation and thus will not be able to establish a connection with a WebSocket server, even with transports: ["websocket"]
engine.io-client:socket creating transport "polling" +0ms
socket.io-parser decoded 4{"message":"No auth token"} as {"type":4,"nsp":"/","data":{"message":"No auth token"}} +732ms
See also
Advertising:
