Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- From: stevehunter_1@xxxxxxxxxxx
- Date: 1 Dec 2006 10:50:07 -0800
Tried to use port 80 for tcp/ip traffic and it worked well except it
impacted some customers with firewalls. Apparently if the traffic
doesnt "look http", it is being discarded. Also there seems to be cases
of persistence -- some firewalls i guess dont let a tcp/ip connection
on port 80 stay open more than X number of minutes.
I am wondering if anyone has successfully deployed a software to many
users using port 80 (tcp/ip) for outbound connections? Any insight
into what i can do with my packet to make it look more http ? What
about the persistence issue?
I dont think i can handle 100% of the scenarios but if anyone has done
this (perhaps using port 80 as primary and if it doesnt work using port
2345 to cover the small % where it doesnt work) and can offer insight?
i am trying to avoid the end user from having to open up outgoing ports
.
- Follow-Ups:
- Re: Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- From: Arkady Frenkel
- Re: Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- From: Alexander Nickolov
- Re: Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- Prev by Date: Re: winsock
- Next by Date: Re: Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- Previous by thread: Re: CMenusWin::CMenusWin() : m_str( m_szText, TEXT_SIZE )
- Next by thread: Re: Any using Port 80 successfully for TCP/IP (non HTTP) traffic?
- Index(es):
Relevant Pages
|