Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So, the question is:
Is there a way to be sure that the client who is trying to connect to my websocket server, is doing this from the webpage that I provide, and not from any other page, or script?
A malicious user/program can connect to this websocket and there is nothing you can do about it (Period end of story). However, the same-origin policy for WebSockets should be very similar to that of XHR. JavaScript on another domain cannot access a WebSocket on your domain unless you explicitly allow it. So this means if someone where to redistribute your content, they would have to use a cross-domain proxy.