Lamp Architecture Deployment Network environment--nginx service configuration

the basic concept of Nigix

The most common use of nginx is to provide reverse proxy service

Then the reverse proxy describes the basic information as follows:
The proxy server accepts requests as intermediaries on the client side, hides real customers, and obtains resources from the server. If the proxy server outside the Great Wall can also help us to achieve the purpose of crossing the Great Wall. And the reverse proxy as the name implies is the proxy server as the intermediary, hide the real service server, this is certainly not to achieve the Great Wall, but to achieve security and load balancing a series of functions. The so-called security refers to the client's request does not fall directly on the intranet server, but through the agent made a layer of turn
, in this layer can achieve security filtering, flow control, anti-DDOS and a series of strategies. While load balancing refers to the number of servers that we can horizontally scale back-end to actually provide services, the agent forwards requests to each server in a regular order, so that the load on each server is nearly balanced. And Nginx is the current popular such a reverse proxy service.
Test environment
SELinux and iptable Disabled
Test domain Name
A Server IP 172.25.39.250 (primary/physical machine)
B Server IP 172.25.39.1
Here are the demo cases under this environment and under the test domain name:

Special Reminders: Specific demonstration cases and instructions in the annex, thank you

This article is from the "12040125" blog, please be sure to keep this source http://12050125.blog.51cto.com/12040125/1853427

Lamp Architecture Deployment Network environment--nginx service configuration