Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this "Nginx basic function example Analysis" article, so the editor summarizes the following contents, detailed contents, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "Nginx basic function example Analysis" article.

1. Static http server

First of all, nginx is a http server, which can present static files (such as html, pictures) on the server to the client through the http protocol. Configuration:

Server {listen 80; # port number location / {root / usr/share/nginx/html; # static file path}}

2. Reverse proxy server

What is a reverse proxy?

The client can access a website application server directly through the http protocol, and the webmaster can add a nginx in the middle. The client requests nginx,nginx to request the application server, and then returns the result to the client. In this case, nginx is the reverse proxy server.

Configuration:

Server {listen 80; location / {proxy_pass http://192.168.20.1:8080; # Application Server http address}}

Since the server can be accessed directly by http, why add a reverse proxy in the middle, isn't it unnecessary? What is the purpose of reverse proxy?

Continue to look down, the following load balancing, virtual hosts, etc., are based on reverse proxy implementation, of course, reverse proxy functions are not only these.

3. Load balancing

When the number of visits to the website is very large, the webmaster is happy to make money at the same time. Because the website is getting slower and slower, one server is no longer enough.

Therefore, the same application is deployed on multiple servers, and the requests of a large number of users are assigned to multiple machines for processing. At the same time, the advantage is that if one of the servers goes down, as long as there are other servers running normally, it will not affect the use of users. Nginx can achieve load balancing through reverse proxy.

Configuration:

Upstream myapp {server 192.168.20.1 server 8080; # Application Server 1 server 192.168.20.2 http://myapp; 8080; # Application Server 2} server {listen 80; location / {proxy_pass Server}}

The above configuration allocates request polling to the application server, that is, multiple requests from one client, which may be processed by multiple different servers. Through ip-hash, requests can be assigned to a fixed server for processing based on the hash value of the client ip address.

Configuration:

Upstream myapp {ip_hash; # assigns the request to a fixed server based on the client ip address hash value to process server 192.168.20.1 server 8080; server 192.168.20.2 ip_hash; 8080;} server {listen 80; location / {proxy_pass server}}

In addition, the hardware configuration of the server may be good or bad. If you want to allocate most of the requests to good servers and a small number of requests to poor servers, you can control them through weight.

Configuration:

Upstream myapp {server 192.168.20.1 server 8080 weight=3; # this server processes 3x4 requests server 192.168.202server 808080; # server defaults to 1, and this server handles 1CM4 requests} server {listen 80; location / {proxy_pass http://myapp;}}

4. Virtual host

Some websites have a large number of visitors and need load balancing. However, not all websites are so good, and some sites, due to the small number of visitors, need to save costs and deploy multiple sites on the same server.

For example, www.aaa.com and www.bbb.com are deployed on the same server, and the two domain names are resolved to the same ip address, but users can open two completely different websites through the two domain names without affecting each other, just like visiting two servers, so they are called two virtual hosts.

Configuration:

Server {listen 80 default_server; server_name _; return 444; # filter requests from other domain names and return 444 status code} server {listen 80; server_name www.aaa.com; # www.aaa.com domain name location / {proxy_pass http://localhost:8080; # corresponding port number 8080} server {listen 80; server_name www.bbb.com # www.bbb.com domain name location / {proxy_pass http://localhost:8081; # corresponding to port number 8081}}

An application is opened on servers 8080 and 8081 respectively. The client accesses through different domain names and can reverse proxy to the corresponding application server according to server_name.

The principle of virtual host is realized by whether the host in the http request header matches server_name. Interested students can study the http protocol.

In addition, the server_name configuration can also filter someone to maliciously point certain domain names to your host server.

5 、 fastcgi

Nginx itself does not support languages such as php, but it can use fastcgi to throw requests to certain languages or frameworks for processing (such as php, python, perl).

Server {listen 80; location ~\. Php$ {include fastcgi_params; fastcgi_param script_filename / php file path $fastcgi_script_name; # php file path fastcgi_pass 127.0.0.1 location 9000; # php-fpm address and port number # another way: fastcgi_pass unix:/var/run/php5-fpm.sock;}}

In the configuration, requests that end with .php are handed over to php-fpm for processing through fashcgi, and php-fpm is a fastcgi manager for php. Other materials are available for fashcgi, which are not covered in this article.

What's the difference between fastcgi_pass and proxy_pass? The following picture shows you clearly:

The above is about the content of this article "Nginx basic function example Analysis". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more related knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.