Socket connection on port 80. Are there pitfalls?

Question

Programming

We have a real-time flash browser toy that exchanges data with the server via a socket (long polling was dropped due to various considerations). Hung up a socket on the 80th port as it is open at all. So the question arises - what can be troubles with this?
So far, it is not possible to test on a large number of users.

Answer 1

Problems may arise when using an http proxy. The port seems to be open, but the game will not work.

Answer 2

Skype loves to use port 80, apparently for the same reasons. This is disabled in the settings, but you won’t ask all users to climb there ...

Answer 3

For users sitting behind proxies, there should be problems, since proxy servers expect that the traffic that goes through them conforms to the HTTP protocol. If you run your own special protocol, then you will have problems.

Answer 4

I don't think so. Socket doesn't matter. And what kind of troubles do you assume?

Answer 5

For some users, port 80 is definitely busy ...

Answer 6

Some corporate proxies with a traffic filtering function, such as Kerio WinRoute Firewall, do not allow normal work with raw sockets if the connection goes to port 80, even if filtering is disabled.

Answer 7

Ahem... As I said above, use port 443 better, for it, by default, the CONNECT method is allowed in the squid (and in other proxies).