Protocol
SOCKS operates at a lower level than HTTP proxying: SOCKS uses a handshake protocol to inform the proxy software about the connection that the client is trying to make, and then acts as transparently as possible, whereas an HTTP proxy may interpret and rewrite headers (say, to employ another underlying protocol, such such as FTP; however, an HTTP proxy simply forwards an HTTP request to the desired HTTP server). Though HTTP proxying has a different usage model in mind, the CONNECT method allows for forwarding TCP connections; however, SOCKS proxies can also forward UDP traffic and work in reverse, while HTTP proxies cannot. HTTP proxies are traditionally more aware of the HTTP protocol, performing higher-level filtering (though that usually only applies to GET and POST methods, not the CONNECT method).[W]
id | protocol | count |
---|---|---|
1 | SOCKS | 547 |
2 | SOCKS5 | 347 |
3 | SOCKS4 | 200 |
4 | HTTP | 17 |
5 | HTTPS | 2 |
NOTE: TP: Transparent Proxy; AP: Anonymous Proxy; DP: Distorting Proxy; HAP: High Anonymity Proxy.