Skip to content

Conversation

@danielburhans
Copy link

I am semi-new to Node.JS but this was a simple add-in for configuring socket.io to support hostname/network interface binding specifics, as I do not see a way to directly assign socket.io to a specific network interface.

The only draw back I can see is that host gets passed into https createServer as an option, but it does not seam to affect server creation.

@DavidChouinard
Copy link

Why isn't this pull request accepted? I too would like this feature.

@DylanArnold
Copy link

I'm looking for this feature too. Will probably monkey patch in the meantime.

@rauchg
Copy link
Contributor

rauchg commented Jul 5, 2012

The reality is that you can still pass a http server. listen provides a shortcut for quick examples, but the goal is not to keep up with the server API at all points.

@DylanArnold
Copy link

Ah right, thanks for pointing that out!

@rauchg rauchg closed this Dec 9, 2013
darrachequesne pushed a commit that referenced this pull request Jul 4, 2024
Fix incorrect ports in connection URL
darrachequesne pushed a commit that referenced this pull request Jul 8, 2024
The "addTrailingSlash" option allows to control whether a trailing
slash is added to the path of the HTTP requests:

- true (default): "/engine.io/"
- false: "/engine.io"

Related: socketio/engine.io-client@21a6e12

Signed-off-by: iifawzi <iifawzie@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants