Greetings robartes,

It could be that the AIM and MSN Messenger clients attempt a CONNECT first, then on failure try a GET/POST instead. I've heard that AIM actually tries a few different ports, eventually dropping to HTTP GET on 80. Perhaps Trillian attempts CONNECT, fails, complains, and stops.

If this is the case, would looking at Net::HTTPTunnel be worth my time? Or perhaps another solution?

The other idea I had (again, from the brain of a networking newbie) was to create a custom client/server proxy pair. The client would sit on my system and act just like a proxy except that it would convert all requests to it into HTTP GET on port 80 and ship them to the "server". That server is, say, my box at home. It would pick up the requests, translate them back, gather data, ship back to me in my isolation chamber here at the office.

Is this a dumb idea?

gryphon
code('Perl') || die;