Port 443
I've noticed that a lot of games use non standard ports.. the problem is that a lot of firewalls block these non standard ports and you end not being able to play multiplayer games with the outside world (for example: At College)
I'm wondering if its an inherently a bad design to just design games that stick with the use port 443? In my experience firewalls don't block this port because of HTTPS using the same port. Just out of curiosity, why do commercial games always pick these non standard ports?
Quote:Original post by InstigatorOnly one application at a time can listen on the same port, so an ssh server will nuke your application.
I'm wondering if its an inherently a bad design to just design games that stick with the use port 443? In my experience firewalls don't block this port because of HTTPS using the same port. Just out of curiosity, why do commercial games always pick these non standard ports?
Quote:Original post by swiftcoderQuote:Original post by InstigatorOnly one application at a time can listen on the same port, so an ssh server will nuke your application.
I'm wondering if its an inherently a bad design to just design games that stick with the use port 443? In my experience firewalls don't block this port because of HTTPS using the same port. Just out of curiosity, why do commercial games always pick these non standard ports?
That would explain that. But wouldn't the best solution be (on the development side) to let the user choose a port number rather than it being a hard coded port number...
Quote:Original post by Instigator
I'm wondering if its an inherently a bad design to just design games that stick with the use port 443? In my experience firewalls don't block this port because of HTTPS using the same port. Just out of curiosity, why do commercial games always pick these non standard ports?
So they can register them.
In general, services under <1024 are best used for protocols associated with them.
Another issue is that port alone isn't enough to get through firewall. Those can inspect contents of the packet as well, and verify that it really it claims to be.
This is especially problematic with HTTP ports, which may be subject to caching or further inspection, so unless you're really sending HTTP content, connections may get discarded.
I suggest looking into HTTP Upgrade (101 status) and the CONNECT method if you really want to get through where firewalls block most ports.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement