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

Understanding namespaces inside the client URLs #7

Open
jjoschyy opened this issue Aug 7, 2011 · 0 comments
Open

Understanding namespaces inside the client URLs #7

jjoschyy opened this issue Aug 7, 2011 · 0 comments

Comments

@jjoschyy
Copy link

jjoschyy commented Aug 7, 2011

Hello

Thanks a lot for the spec. Except for "namespaces", i was able to get a good understandment of the Socket.IO Protocol. The following questions occured. Is it right that:

  • On a "handshake" the namespace is NO part of the URL (e.g. http://localhost/socket.io/1)?
  • On creating a websocket transport connection, the namespace is NO part of the URL (e.g. ws://localhost/socket.io/1/websocket/234234234)?

If I replace "socket.io" inside the URL with a custom namespace, i got no valid connection. The server says "non-socket.io upgrade". Therefore, in which URL do I have to set the namespace?

Best regards,
Joachim

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