Is there ever any situation where a Windows Store (i.e. Metro) app is allowed by the system to connect to a particular host via a WebSocket, but not to attempt a raw TCP connection to it?
Share
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.
Is there ever any situation where a Windows Store (i.e. Metro) app is allowed by the system to connect to a particular host via a WebSocket, but not to attempt a raw TCP connection to it?
You are asking for “app is allowed by the system“, but you should take into account not only the two endpoints involved (client, server), but also the network in between and any intermediaries like firewalls, proxies and the like.
Due to it’s HTTP compatible initial handshake, a WebSocket connection is more likely to succeed than a raw TCP connection on some arbitrary port.
However, if you compare the success rates of a secure WebSocket connection on standard port 443, with a raw TLS/TCP connection also on port 443, those might be similar.
Usually, intermediaries won’t be able to intercept, inspect or block TLS/443 .. if they want to allow HTTPS ..