i cant see the mir client talking HTTP tho? For instance, The proxy server at my school ONLY allows http traffic through, and only on ports 80 and 443, and it actively scans the traffic to prevent bad words and non-http stuff etc appearing.
So in my situation, i would need a client side app, that listened on the 3 ports, and a server side app listening on port 443, then the client would connect to the client side app, which would talk ssl to the server-side app which would then communicate with the mir server however you do (the destination ports would need to be encoded in the traffic)
The next problem with the use of proxies, is that to send data, you need to use POST (GET doesn't allow long enough data iirc), and (at least with SQUID) you cant send the data, receive some data, send some more etc - you need either a GET that is connection: keep-alive that just recieves data and then post data separetly in packets, or post data every second (either waiting data, or blank) and get the data that way)
Short story, this prolly wont work on the tight setups