Today, I have been working early, and the agent software is charged. Ugh! Invasive, find a day of protocol conversion tool. Although it is very boring, it is still a bit of stuff! At most least, I know that HTTP is converted to SOCKS! (In fact, if you want to open SOCKS, take your own relationship with the network management, huh, 冇 冇 problem D! ^ O ^)
In the process of finding tool software, I have found two kinds of tools that should be more classic! One is SOCKS2HTTP and the other is Sockscap32. These two tools add together (of course, the two software are not the same company!), That breakthrough HTTP limit is easy! ^ o ^
When using SocksCap32 with Socks2HTTP, it is probably that the principle is like this: (here, it does not use the method, it seems that both tools have Chinese version! So just the principle!) Local SOCKS tool software sends a SOCKS packet, In the process (not sent out) is received by SOCKS2HTTP, then SOCKS2HTTP transfers packets to HTTP packets to the server. In the backhaul data HTTP package of the server, it is converted to the SOCKS data transfer to the SOCKS data transfer by the local machine's SOCKSCAP32. The conversion process of the entire protocol has a local machine.
With the agent software TTT and Socksonline used at the time, our machine just acts as a SOCKS turn HTTP package and unpacking process. When our SOCKS tool forwards the packet, the packet is not directly transmitted to the address pointed by the original, but is packed by the agent software to the agent software HTTP-Tunnel server (HTTP-Tunnel server) Not our proxy server, but we use the server for breakthrough 80 port restrictions. Our proxy server is just an 80-port HTTP server. In the packaged protocol packet, it is completely secular with http, so For our proxy server, it is transparently transmitted). When the data arrives at the agent HTTP-Tunnel server, the agent HTTP-TUNNEL server will turn the data package to the socks normal data, and then send the data to the address of the original pointing. Then, our destination address server returning SOCKS data is not directly transferred to us, but it is passed to the agent HTTP-Tunnel server. The SOCKS packet is packaged into the HTTP protocol forwarding to us by the agent http-tunnel server! Finally, our agent software receives the packaged packet, and it is again converted from http to SOCKS from HTTP after the software's shell protocol.
Such a loop process is the principle of QQ, etc. on HTTP! ^ o ^
================
Today is not your mood! I have a lot of fifts! See the nausea of vomiting blood! Ugh! failure!
Finally, leave a few better protocol conversion tool software: icqProxyhttp-tunnelhttpporte-borderclientfilegateway and the two I have said! It's all good!
