Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
toji opened this issue Sep 29, 2011 · 0 comments
Closed

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

toji opened this issue Sep 29, 2011 · 0 comments

Comments

@toji
Copy link

toji commented Sep 29, 2011

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?

This issue was closed.
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

No branches or pull requests

1 participant