networking - Using HTTP port to evade firewall -
i'm creating client-server application communicates via custom socket protocol. i'd client usable within networks have restrictive firewall (corporate, school, etc.). done connecting via http, since that's available.
if want that, have use http or enough use custom protocol via server port 80?
the firewall may have more restricted checks restricting ports, , might have proxies along way, , deal in http.
still, using well-known port other normal use still far better many schemes inherently non-http stuff on http, , implement rfc 3093 (when people implement april fools rfcs shows combination of humour , technical acumen, rfc 3093 exception).
to around proxy issue, use 443 rather 80, https traffic can't proxied in quite same way. indeed, don't need use ssl, proxy assume can't see it.
none of needs done application though. application needs have port configurable (that should done server application anyway). default should away well-known ports, sysadmin able use 80 or 443 or whatever if they need to.
Comments
Post a Comment