-
-
Notifications
You must be signed in to change notification settings - Fork 82
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 is not getting connected #30
Comments
Hello @manusaxena, Please give me a feedback, if you have done :) |
i have changed my url now. but still having "Invalid Sec-WebSocket-Accept response." please suggest any pointers |
Can you share your url? So I can try either |
i have created javascript client with same stomp protocol and it is working. please visit this link as well . |
Can you try this url: ws://205.147.102.113/bitbuddy/bitbuddyLead/gateway/websocket |
Above is not working because backend end point is not available for this url. |
I'm on work right now, when I go home I'm going to try your url very fast |
thanks for very prompt replies. appreciate it |
i got to get resolve. Backend is based on sockJs protocal, so i need to add couple of url params. |
@manusaxena Hi, can you provide params you've added? I'm having same issue |
@cleverClosure Hi. Have you solved this problem? |
i have tried to connect with socket and my delegate is landing to didSendError always with message
Invalid Sec-WebSocket-Accept response.
why example is adding gateway/websocket to url. is it necessary to add it
The text was updated successfully, but these errors were encountered: