Re: Wrapping TCP communications in HTTP
- From: Steve Alpert <sra@xxxxxxxxxxxxxxxxx>
- Date: Mon, 05 Dec 2005 12:26:18 -0500
Mick wrote:
We have a set of applications that use TCP sockets (winsock2) to communicate between machines. To communicate, a client machine establishes a TCP socket connection to a server, then sends and receives messages using our own proprietary protocol. We have developed and tested all of this and it works fine. Now, because of firewall security issues at some of our customer sites, we would like to wrap these communications in the HTTP protocol. Is it possible to do this? If so, what would be required to implement this?
I know very little about HTTP, but my understanding is that HTTP communications requires that you establish a session with a server, send request messages to the server, and then wait to receive a response. Would this require us to scrap our existing socket implementation, or can we just wrap our messages in HTTP?
Any advice on how to implenent this will be much appreciated. Thanks!
Although likely, most firewalls block ports and not protocols. That suggests they leave open port 80 (assuming http) and 443 (assuming https). They MAY check the envelopes but then again, maybe not!
/steveA
-- Steve Alpert my email Fgrir_Nycreg @ vqk.pbz is encrypted with ROT13 (www.rot13.org) and spaces
.
- Follow-Ups:
- Re: Wrapping TCP communications in HTTP
- From: Alexander Nickolov
- Re: Wrapping TCP communications in HTTP
- Prev by Date: Re: How to debug MFC or Win32 DLL ?
- Next by Date: LSP HTTP redirecting
- Previous by thread: Re: Wrapping TCP communications in HTTP
- Next by thread: Re: Wrapping TCP communications in HTTP
- Index(es):
Relevant Pages
|