Rich Fife <rfife@amug.org> writes:

> Hello all,
>
> Hope this isn't a total newbie question...
>
> I'm writing an extension to an existing client / server suite that
> currently uses UDP for all of its communication.
>
> We are having some problems with clients that are behind firewalls
> that only allow HTTP and HTTPS, so I've created a system where the
> necessary communications all take place in the form of GET and PUT
> HTTP calls. This makes the proxy think that the client is simply
> browsing the web when they are not. Yeah, lame, but it works for
> HTTP. I need to implement a version that uses HTTPS as well. I've
> got all my certificates ready and it works between the client and the
> server if there is no proxy, but the question I'm having trouble
> answering is how do you implement HTTPS from the TCP / SSL level?
>
> Do you send an unencrypted HTTP header and then pop over to SSL
> immediately afterwards? When do you do the SSL handshaking? Before
> or after you send the header?
>
> Thanks in advance!

stunnel is a command line thingee built with such issues in mind.

http://www.stunnel.org/examples/


--
Todd H.
http://www.toddh.net/