Nginx scenario practice

This article mainly introduces the scenario practice of Nginx, which has certain reference value. Now I share it with everyone. Friends in need can refer to it

1. Nginx as a static resource Web service

1. Dynamic resources and static resources

If the page requested by the client is a static web page, the server will directly respond to the client with the content of the static web page. If the client requests a dynamic web page, the server needs to first replace the dynamic web page with a static web page, and then respond to the converted static web page to the client

Several types of static resources

• Browser rendering: HTML, CSS, JAVASCRIPT

• Pictures: JPEG, GIF, PNG...

• Video : FLV, MPEG...

• File: TXT, etc. Any download file

2, CDN (Content Delivery Network) content distribution network

The basic idea is to avoid bottlenecks and links on the Internet that may affect the speed and stability of data transmission as much as possible, so as to make content transmission faster and more stable. By placing node servers throughout the network to form a layer of intelligent virtual network based on the existing Internet, the CDN system can real-time analyze the network traffic and the connection and load status of each node, as well as the distance to the user and response time. and other comprehensive information to redirect the user's request to the service node closest to the user. Its purpose is to enable users to obtain the required content nearby, solve the congestion situation of the Internet network, and improve the response speed of users' access to the website.

3. Configuration syntax

1. sendfile (file reading)

• Configuration syntax: sendfile on|off ;

• Default: None

• Context: http, server, location, if in location

• Configuration syntax: tcp_nopush on|off;

• Default: None

• Context: http, server, location

• Configuration syntax: tcp_nodely on|off;

• Default: None

• Context: http, server, location

• Configuration syntax: gzip on|off;

• Default: None

• Context: http, server, location, if in location

• Configuration syntax: gzip_comp_level level;

• Default: none;

• Context: http, server, location

• Configuration syntax: gzip_http_version 1.0|1.1;

• Default: None

• ##Context: http, server, location

• Configuration syntax: gzip_static on|off|always;

• Default: gzip_static off;

• Context: http, server, location

• The browser has no cache:

• Browser request → No cache → Request WEB server → Request response, negotiate → Present

• The client has cache

• Browser request→with cache→verification expiration→present

• Verification expiration mechanism

• First request:

• Second request Request:

• ##expires (response headers add Cache-Control and Expires)

• Configuration syntax: expires [modified] time; expires epoch |max |off;

• Default: expires off;

• Context: http, server, location, if in location

• add_header

• Configuration syntax: add_header name value [always];

• Default: None

• Context: http, server, location, if in location

• Configuration syntax: valid_referers none|blocked|server_names|string...;

• Default: None

• Context: server, location

valid_referers none blocked IP
if($invalid_referer) {
    return 403;
}

Copy after login

Reminder: You can use curl to test the configured anti-leech: curl -e "http:www.baidu.com" -I IP

• Forward proxy

• The object is the client ( For example, if you want to access the external network, set the proxy server to the proxy address, and the client can access any website)

• Reverse proxy

• The object is the server (you don’t need to care which server you are accessing, the reverse proxy is placed on the server. The reverse proxy will help us handle the request)

• proxy_pass

• Configuration syntax: proxy_pass URL;

• Default: None

• Context: location, if in location, limit_except

Supplementary:

• proxy_buffering (buffer)

• Syntax configuration: proxy_buffering on | off;

##Default: none;
Context: http, server, location
Extensions: proxy_buffer_size, proxy_buffers, proxy_busy_buffers_size

proxy_redirect (jump redirect)
Configuration syntax: proxy_redirect default;proxy_redirect off;proxy_redirect redirect replacement;
Default: none
Context: http, server, location

proxy_set_header (header information)
Configuration syntax: proxy_set_header file value;
Default: proxy_set_header Host $proxy_host;proxy_set_header Connection close;
Context: http, server, location

• ##Extensions: proxy_hide_header, proxy_set_body

• ##proxy_connect_timeout (timeout)

• Configuration syntax: proxy_connect_timeout time;

• Default: None

• Context: http, server, location

• Extensions: proxy_read_timeout, proxy_send_timeout

• ##Example in configuration file:

  proxy_pass http://127.0.0.1:8080;
  proxy_redirect default;
  
  proxy_set_header HOST $http_host;
  proxy_set_header X-Real-IP $remote_addr;
  
  proxy_connect_timeout 30;
  proxy_send_timeout 60;
  proxy_read_timeout 60;
  
  proxy_buffer_size 32k;
  proxy_buffering on;
  proxy_buffers 4 128k;
  proxy_busy_buffers_size 256k;
  proxy_max_temp_file_size 256k;

  Copy after login
3. Nginx as a load balancing service

Load Balancing

Load balancing, the English name is Load Balance, means to allocate execution to multiple operating units, such as Web servers, FTP servers, enterprise key application servers and other mission-critical servers, etc., so as to jointly complete work tasks.

upstream

• Configuration syntax: upstream name {...}

• Default: None

• Context: http

• ##Simple configuration example

  :

upstream ronaldo {
        server ip:port [param];
        server ip:port [param];
        server ip:port [param];
}
server {
    location / {
        proxy_pass http://ronaldo;
    }
}

Copy after login

param参数解释：

调度算法：

• ip_hash：

• 只需要在upstream中加入 ip_hash; 即可

• 缺陷：如果走代理，那么remote_addr就不是用户真实的ip

• url_hash（1.7.2版本以后可用）：

• 配置语法：hash key [consistent];

• 默认：无

• Context：upstream

key可以是$request_uri，根据url进行hash

四、Nginx作为缓存服务

1、缓存的类型

• 服务端缓存。例：memcache、reids

• 代理缓存。例：Nginx缓存服务端的数据

• 客户端缓存。

2、常用缓存配置

• proxy_cache_path

• 配置语法proxy_cache_path path [levels=levels] [use_temp_path=on|off] keys_zone=name:size [inactive=time] [max_size] [use_temp_path]...

• 默认：无

• Context：http

• proxy_cache

• 配置语法：proxy_cache zone | off;

• 默认：proxy_cache off;

• Context：http，server，location

• proxy_cache_valid（缓存过期周期）

• 配置语法：proxy_cache_valid [code...] time

• 默认：无

• Context：http、server、location

• proxy_cache_key（缓存的维度）

• 配置语法：proxy_cache_key string;

• 默认：proxy_cache_key $scheme$proxy_host$request_uri;

• Context：http、server、location

常见配置：

proxy_cache_path cache_path levels=1:2 keys_zone=key_name:10m max_size=10g inactive=60m use_temp_path=off;

server {
    loaction / {
        proxy_pass http://ronaldo;
        proxy_cache key_name;
        proxy_cache_valid 200 304 12h;
        proxy_cache_valid any 10m;
        proxy_cache_key $host$uri$is_args$args;
        add_header Nginx-Cache "$upstream_cache_status";

        proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
    }
}

2、清除指定缓存

• rm -rf 缓存目录内容

• 第三方扩展模块：ngx_cache_purge

3、如何让部分页面不缓存

• proxy_no_cache

• 配置语法：proxy_no_cache string ...;

• 默认：无

• Context：http，server，location

简单示例

if ($request_uri ~ ^/(url_3|login|register|password\/reset)) {
    set $cookie_nocache 1;
}

location / {
    proxy_no_cache $cookie_nocache;
}

4、大文件分片请求

• slice

• 语法配置：slice size;

• 默认：slice 0;

• Context：http、server，location

优势：每个子请求收到的数据都会形成一个独立的文件，一个请求断了，其他请求不受影响。
缺点：当文件很大或者slice很小的时候，可能会导致文件描述符耗尽等待情况。

相关推荐：

关于Nginx的基础内容

Nginx编译安装Lua模块

The above is the detailed content of Nginx scenario practice. For more information, please follow other related articles on the PHP Chinese website!