HTTP Proxy. Let's talk about HTTP proxies first. There are actually two types of HTTP proxies. One is a reverse proxy such as Nico and Jinx, which is not shown here. The other type is a tunnel proxy, and we will mainly expand on this kind of proxy. It can proxy any content based on TCP. Note that there is a misunderstanding here. Many people think that HTTP proxy can only proxy HTTP content, but it can also proxy HTTPS and any TCP-based content, but can't proxy UDP content. We will see why it can't proxy UDP content later. Suppose there is an HTTP proxy server. The address that a client wants to proxy. Let's assign roles here. A client may be a Chrome browser or a curl command. The HTTP proxy server is the server. The interaction between client and server is as follows. Step One, client-server sends the address to be proxied. Step 2, server-client response result. Then the tunnel is established, and the client and server can transmit content to each other through this tunnel. Question one: Where is the domain name resolved? The proxy address is passed from the client to the server. If the client passes a domain name address, the domain name will be resolved on the server. Of course, it is also possible that the client pre-resolves the IP of the domain name locally and then passes it to the server's IP address. So where the domain name is resolved depends entirely on the role of the client that initiated the request in the first place.
Socks 5 Proxy. Let's talk about the socks 5 proxy again. It can proxy any TCP-based content as well as UDP content. But, in fact, many socks 5 proxy servers do not implement UDP support. You can use the bellbrook test socks 5 command to test whether a socks 5 server supports UDP. Suppose there is a socks 5 server. The TCP address that a client wants to proxy. Let's assign roles. Here a client may be a Chrome browser, a curl command, or a game client. The Socks 5 server is the server. The interaction between the client and the server is as follows. For the convenience of understanding, the original protocol is abstracted into human-readable content. Step one, client-server asks the protocol, version, and authentication method. Step 2, server-client response protocol version and authentication method. Step three, client-server If the server needs authentication, send the authentication information. Step 4, server-client If the server needs authentication, respond to the authentication result. Step 5, client-server send the address to be proxied. Step 6, server-client response result. Then the tunnel is established, and the client and server can transmit content to each other through this tunnel. We noticed that the whole process between the client and the server is the TCP protocol. The UDP address a client wants to proxy. The interaction between the client and the server is as follows, and for the convenience of understanding, the original protocol is abstracted into human-readable content.
Q: Where is the domain name resolved in the HTTP Proxy Protocol?
A: The domain name can be resolved either on the server or on the client side before passing the IP address to the server. It depends on the role of the client that initiated the request.
Q: What types of content can an HTTP Proxy proxy?
A: An HTTP Proxy can proxy any content based on TCP, including HTTP, HTTPS, and any TCP-based content. However, it cannot proxy UDP content.
Q: What is the main type of proxy discussed in the HTTP Proxy Protocol section?
A: The main type of proxy discussed is the tunnel proxy, which can proxy any content based on TCP.
Q: What is the role of the client and server in the interaction described in the HTTP Proxy Protocol section?
A: The client initiates the request by sending the address to be proxied, and the server responds with the result. A tunnel is then established for content transmission.
Q: What is the Socks 5 Proxy Protocol?
A: The Socks 5 Proxy Protocol is a protocol that allows for proxying TCP-based and UDP-based content. However, not all socks 5 proxy servers support UDP.
Q: How can you test if a socks 5 server supports UDP?
A: You can use the bellbrook test socks 5 command to test whether a socks 5 server supports UDP.
Q: What types of content can a Socks 5 Proxy proxy?
A: A Socks 5 Proxy can proxy any TCP-based content as well as UDP content, but some servers may not implement UDP support.
Q: What is the main type of proxy discussed in the Socks 5 Proxy Protocol section?
A: The main type of proxy discussed is the socks 5 proxy which can handle TCP-based and UDP-based content.
Q: What is the role of the client and server in the interaction described in the Socks 5 Proxy Protocol section?
A: The client and server exchange protocol and authentication information before the server responds with the result. A tunnel is then established for content transmission.
