Allow for a custom configuration for Socket.IO requests

[MayorX500]

When attempting to connect to a Socket.IO server that uses a non-default handshake path (e.g., /my-custom-path/ instead of /socket.io/), the intuitive approach is to add the path to the main URL in the “Socket.IO Request” type. For example: http://my-api.com/my-custom-path/.

However, when this is done, the application ignores the path provided in the URL. The actual request sent is still directed to the default /socket.io/ endpoint, resulting in a 404 Not Found error from the server and making it impossible to connect. This behavior leads to a frustrating user experience, as the UI's URL preview suggests the correct path will be used, but the underlying request does not honor it.

To solve this and other common configuration challenges, a dedicated “Settings” tab should be added to the “Socket.IO Request” type. This tab would provide clear and explicit control over the connection parameters.

A potential implementation could include the following options:

• Client Version: A dropdown to select the Socket.IO client protocol version to be used (e.g., v3, v4).
• Handshake Path: An input field to set the server path for the handshake request (e.g., /my-custom-path/). This provides an unambiguous way to solve the core problem.
• Handshake Timeout: Set how long the handshake request should wait before timing out (in ms).
• Reconnection Attempts: Maximum reconnection attempts when the connection closes abruptly.
• Reconnection Interval: The delay between each reconnection attempt (in ms).
• Enable TLS verification: A toggle to verify the server certificate when connecting over a secure connection.

[poojithap11]

Hi,

Thank you for your suggestion.

A feature request has been raised to add support for custom handshake paths and additional socket.io connection settings in insomnia.

Thank you.