Usage scenario: It is clearly a transparent proxy, which is used when the client requests the external network. This machine does not have external network permissions and needs to request the public network through the proxy address configured by nginx.
Question: When there is an https link that needs to request the public network, the connection between the client and nginx must be in http mode? It cannot be: the client directly implements the SSL handshake with the origin site through nginx, and then the client decodes it by itself? That is, nginx truly becomes a transparent proxy.
Personally understood, nginx is placed on the server side, and as a proxy for multiple servers, it is a reverse proxy. The client serves as a proxy service for external network requests (it only forwards requests from the real client to the origin site). Isn't this a forward proxy? Why is nginx a reverse proxy?
Sincere thanks...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Nginx is "mainly" used for reverse proxy, at least for me personally. Of course, I also use it as a forward proxy
Nginx does not support "CONNECT", so when the client requests an https site on the external network, an error will occur:
It is recommended to use Squid to build the proxy for the intranet,
But if you insist on Nginx, bring this module and compile it again: