You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: