Our great sponsors
-
nico
A HTTP3 web server for reverse proxy and single page application, automatically apply for ssl certificate, Zero-Configuration. (by txthinking)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Let's talk about HTTP proxies first. There are actually two types of HTTP proxies, one is a reverse proxy, such as nico and nginx, which are not shown here. The other is tunnel proxy. We mainly expand 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, and we'll see why it can't proxy UDP content later.
We know that brook relay can relay any service based on TCP and UDP, just need to specify a from address and a to address. But according to the seventh step of the previous Socks 5 proxy UDP protocol, it is only necessary for the Socks 5 Server to specify the UDP Server that informs the client as the address of the relay server. If you are using brook socks5, you can use the --socks5ServerIP parameter to specify the IP of the UDP Server.