Skip to content

Socket.io and non-domain-level Proxies #543

Closed
@toji

Description

@toji

I have a socket.io server that I am trying to integrate with a larger content server. Since this is one of several services that may be running on this particular server, IT would like to proxy to my service from a sub-directory of the TLD. (ie: http://domain.com/my-service/) Everything else about this setup seems to be working fine (I even got it serving the socket client script properly) except that socket.io refuses to attempt it's connection to anything but http://domain.com, choosing to treat "my-service" as a namespace instead of part of the actual path.

Since there may eventually be other services at this site that require websocket connections, it is not feasible to reroute all domain level socket traffic to my service's proxy. Is there a way that I can force socket.io to attempt it's connection to an exact URL?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions