Days to find tools [protocol conversion]

Today in the early morning to work, the agency software to carry out charges. Alas. Without resistance, find a day of the Protocol conversion tool. Although very boring, but still learned a little dongdong. At the very least, the principle of HTTP conversion to socks is known. (In fact, if you want to open socks words, to their own and network management relationship, Ah, no problem d. ^o^)

In the process of looking for tool software, we found two models which should be regarded as more classic tools. One is socks2http, the other is SOCKSCAP32. These two tools are added together (of course, two software is not the same company.) , that break the HTTP limit is readily available also. ^o^

In the use of socks2http with SOCKSCAP32, probably understand the principle is this: (here does not use, as if two tools have the Chinese version of the. So just talk about the principle. ）
The local Socks tool software sends a SOCKS packet, which is received by socks2http in the process of sending (not yet sent out), and then socks2http converts the packet to HTTP data packages sent to the server. In the HTTP packet of the server's return data, the SOCKSCAP32 of the local machine is converted to the socks data to the tool software. The conversion forwarding process for the entire protocol has local machine completion.

And with the use of the proxy software TTT and Socksonline, our machine just acts as a socks to the HTTP package and reconciliation process. When our Socks tool forwards the packet, the packet is not sent directly to the address that my data originally pointed to, but is packaged by the agent software and forwarded to the proxy software Http-tunnel server (Http-tunnel server is not our proxy server, Instead, we use a server that breaks through the 80-port-limiting agent software. Our proxy server is just a 80-port HTTP server. The packaged protocol packet, which is completely attached to HTTP, is transparent and can be transmitted to our proxy server. When the data arrives at the proxy Http-tunnel server, the proxy Http-tunnel server then turns the packet shelling into socks normal data and sends the data to the address we originally pointed to. Then, our destination address server returns the SOCKS data not directly back to us, but back to the agent Http-tunnel server. Via the proxy Http-tunnel server, the SOCKS packet is then packaged into the HTTP protocol for forwarding to us. Finally, our agent software received the package of packets, after the software to the packet's shelling protocol from HTTP to socks again.

Such a cycle process is the use of HTTP on the principle of QQ. ^o^

================

I'm in a bad mood today. A lot of Fizi. See the nausea that wants to vomit blood. Alas. Failed.

Finally, leave a few better protocol conversion tool software:
Icqproxy
Http-tunnel
Httpport
E-borderclient
Filegateway
And the two that I mentioned above. All right.