Socket.io connection ignores custom path

[erayhanoglu]

Expected Behavior

Socket.io server allows using custom path to serve. Insomnia client should connect using custom paths.

Actual Behavior

Connecting a Socket.IO server on a custom url (wss://localhost:6001/chat) fails. When i debug de request i see that request.url is always /socket.io/?EIO=4&transport=polling&t=tg8wc9np but it should be /chat/?EIO=4&transport=polling&t=tg8wc9np

Reproduction Steps

1. Create a Socket.IO server and listen on a custom path.
2. Try to connect

Is there an existing issue for this?

• I have searched the issue tracker for this problem.

Which sync method do you use?

• Git sync.
• Insomnia Cloud sync.
• Local only

Additional Information

No response

Insomnia Version

12.1.0

What operating system are you using?

macOS

Operating System Version

macOs Tahoe 26.1

Installation method

download from insomnia web

Last Known Working Insomnia version

Version: Insomnia 12.1.0 Build date: 11/21/2025 OS: Darwin arm64 25.1.0 Electron: 38.4.0 Node: 22.20.0 Node ABI: 139 V8: 14.0.365.10-electron.0 Architecture: arm64

[CurryYangxx]

Hi @erayhanoglu , according to Socket.io's doc for the path (https://socket.io/docs/v4/client-options/#path), the path in the URL represents the namespace, not the handshake path. In your demo wss://localhost:6001/chat, chat is not path, it's namespace.

Please note that this is different from the path in the URI, which represents the Namespace.

Currently in Insomnia, we don't support setting the path. I am considering adding a configuration item to do this in the later version. What do you think?

[erayhanoglu]

Thank you for your response. This would be great.

[CurryYangxx]

@erayhanoglu We just released v12.5.0-beta.0 to support this feature. Feel free to try it and welcome any feedback. Thanks!