Difference between revisions of "Socket.io-client"

From wikieduonline
Jump to navigation Jump to search
Tags: Mobile web edit, Mobile edit
 
(3 intermediate revisions by the same user not shown)
Line 10: Line 10:
  
 
<code>socket.io-parser decoded 4{"message":"[[No auth token]]"} as {"type":4,"nsp":"/","data":{"message":"[[No auth token]]"}} +732ms</code>
 
<code>socket.io-parser decoded 4{"message":"[[No auth token]]"} as {"type":4,"nsp":"/","data":{"message":"[[No auth token]]"}} +732ms</code>
 +
 +
[[No auth token]]
 +
[[Signature verification failed]]
 +
 +
 +
client.on("connect_error", (err) => {
 +
  console.log(`connect_error due to ${err.message}`);
 +
});
  
 
== Related ==
 
== Related ==
 
* <code>[[wscat]]</code>
 
* <code>[[wscat]]</code>
 +
* <code>[[DEBUG=* node your_app.js]]</code>
  
 
== See also ==
 
== See also ==

Latest revision as of 16:28, 14 March 2023

npm install socket.io-client

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

No auth token
Signature verification failed


client.on("connect_error", (err) => {
  console.log(`connect_error due to ${err.message}`);
});

Related[edit]

See also[edit]

Advertising: