Socket.IO Tester
Connect to a Socket.IO server, send JSON or binary events, wait for acknowledgements and inspect namespace and transport events.
Connecting sends data directly to the specified server.
Connect to the correct namespace
Enter an HTTP(S) origin without a pathname or query. Set the Engine.IO path separately from the Socket.IO namespace: /socket.io/ and / are the defaults. Authentication accepts a JSON object; query accepts an object of scalar values without reserved Engine.IO keys. Example fills an illustrative origin without connecting.
This tool bundles socket.io-client 4.8.4, using Engine.IO protocol 4 and Socket.IO protocol 5. It targets compatible Socket.IO 3.x/4.x servers, not Socket.IO 1.x/2.x, raw WebSocket, MQTT or SSE. Server compatibility and enabled transports must be checked for your endpoint.
Send arguments and inspect replies
JSON mode expects an argument array: [{"message":"hello"},42] sends two arguments, not one JSON string. Binary hex mode sends one byte array. Incoming binary values are exported as objects with $binary hexadecimal data and a bytes count; this describes the received bytes rather than the server’s original JavaScript object type.
Request an acknowledgement to attach a callback with a 1–30 second timeout. Ack results are logged separately from incoming events; a timeout does not prove the server did not process the event. Each click sends once, with no automatic retries. Incoming events requiring a client acknowledgement are flagged but are not automatically acknowledged.
Transports, credentials and lifecycle
Auto begins with polling and may upgrade to WebSocket. Polling-only and WebSocket-only modes help diagnose transport problems. Credentials Include controls cross-origin polling credentials; a browser WebSocket handshake can include eligible cookies independently of that option. Polling requires CORS, and all transports remain subject to server Origin checks, TLS and browser security policies. Custom handshake headers are not exposed.
Connection timeout is 1–30 seconds. Automatic reconnection is disabled: reconnect explicitly after a disconnect. Changing connection settings closes the old manager and clears the report; changing event arguments keeps the connection. Disconnect and Clear close the session, and leaving the page releases it. No connection or authentication settings are persisted.
Bounded logs and exports
Up to 1,000 records or 2 MiB of serialized log data are retained; exceeding the cap disconnects. An event argument payload is limited to 1 MiB, 32 outgoing JSON arguments, nesting depth 32 and 10,000 inspected nodes. Up to 20 acknowledgement callbacks may be pending; a transport backlog above 100 packets blocks further sends. The library and browser may receive a packet before these application checks run.
Preview stops at 200,000 characters while Copy and Download report export the whole retained report. Authentication is not copied into the connection log, though a server may echo it in event data. This is a manual protocol client, not a load tester or a delivery-guarantee checker.
Questions & answers
Why does a WebSocket echo server fail?
Socket.IO adds Engine.IO handshakes and its own packet protocol. Use the WebSocket Tester for a raw WebSocket endpoint.
Is a missing acknowledgement the same as a failed event?
No. The server may have processed the event without calling the acknowledgement, or the reply may have been lost. Retrying an operation can duplicate its effects.
Other Languages
References
How we make sure
We check this tool with the automated test suites linked below. Example checks are shown in their original language.
- Verification method
- Connect to a real local Socket.IO server and check namespaces, auth/query, JSON, binary, acknowledgements, timeout and disconnect.
- Comparison reference
- Interoperability between a socket.io server and the page’s Socket.IO client.
- Verification scope
- This is protocol integration, not comparison between independent Socket.IO engines.
Test source and cases (select a file to read it)
-
stream-tools.test.js
- Socket.IO options separate origin, engine path, namespace and protocol transports
- Socket.IO JSON argument arrays and exact binary payloads reject reserved names and bad formats
- Socket.IO log normalization preserves nested binary, rejects huge/deep/cyclic data and prototype keys safely
- Socket.IO actual server checks namespace/auth/query, JSON, binary, acknowledgements and manual disconnect
- Socket.IO actual acknowledgement timeout, server rejection, stale generation and pending cap
- Socket.IO connection deadline covers an unacknowledged namespace after Engine.IO is open
These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.