nginx 反向代理配置(一)

#① part start
#运行nginx进程的账户
user www;
#
worker_process 1;
error_log /var/log/nginx/error.log
pid /var/run/nginx.pid;events{
use epoll;
worker_connections 1024;
}http{
include /etc/nginx/mime.types;
default_type application/octet-stream;
access_log /var/log/nginx/access.log main;
#
sendfile on;
#
keepalive_timeout 65;
gzip on; index index.html index.htm;
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
#② part start
# 定义上游服务器列表组
upstream web1 {
server 127.0.0.1:111 weight=1;
server 127.0.0.1:222 weight=1;
}
upstream web2 {
server 127.0.0.2:111 weight=1;
server 127.0.0.2:222 weight=6;
server 127.0.0.2:333 weight=7;
}
#定义一个服务器，其监听80端口，配置的域名是www.company.com
server{
listen 80;
# using www domain to access the main website
server_name www.company.com;
access_log /var/log/nginx/www.log location / {
root /home/website_root; }
}
#③ part start
#定义第二个服务器，其同样监听80端口，但是匹配域名是web.company.com
server{
listen 80;
# using web sub domain to access
server_name web.company.com;
access_log /var/log/nginx/web_access.log location / {
root /home/web2_root;
proxy_pass http://127.0.0.1:8080/web/;
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
}
}
#定义第三个服务器，其同样监听80端口，但是匹配域名是web1.company.com，并把请求转发到web1上游服务
server{
listen 80;
# using web1 sub domain to access
server_name web1.company.com;
access_log /var/log/nginx/web1_access.log location / {
root /home/web1_root;
proxy_pass http://web1;
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
}
}
#定义第三个服务器，其同样监听80端口，但是匹配域名是web2.company.com，并把请求转发到web2上游服务
server{
listen 80;
# using web2 sub domain to access
server_name web2.company.com;
access_log /var/log/nginx/web2_access.log location / {
root /home/web2_root;
proxy_pass http://web2;
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
}
}
}

upstream blog.xsgzs {
server 127.0.0.1:4000
}upstream admin.xsgzs {
server 127.0.0.1:3009
}

server {
listen 80;
server_name www.blog.xsgzs.com;
location / {
proxy_pass http://blog.xsgzs;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
} server {
listen 80;
server_name www.admin.xsgzs.com;
location / {
proxy_pass http://admin.xsgzs;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
}

(1) main 全局设置
(2) events (nginx 工作模式)
(3) http (http设置)
(4) server (主机设置)
(5) location (URL匹配)
(6) upstream (负载均衡服务器设置)

user nobody nobody;
worker_processes 2;
error_log /usr/local/var/log/nginx/error.log notice;
worker_rlimit_nofile 1024;

user user [group]

nginx: [emerg] getpwnam("test_user") failed (2:No such file or directory) in /Nginx/conf/nginx.conf:2

worker_processes number | auto

events {
use epoll; #Linux平台
worker_connections 1024;
}

worker_connections number

* soft nofile 327680
* hard nofile 327680

ulimit -n 327680

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63704
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 327680
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 63704
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

http{
include mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /usr/local/var/log/nginx/access.log main;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 10;
#gzip on;
upstream myproject {
.....
}
server {
....
}
}

server {
listen 8080;
server_name localhost 192.168.12.10 www.yangyi.com;
# 全局定义，如果都是这一个目录，这样定义最简单。
root /Users/yangyi/www;
index index.php index.html index.htm;
charset utf-8;
access_log usr/local/var/log/host.access.log main;
error_log usr/local/var/log/host.error.log error;
....
}

root path

location /data/
{
root /locationtest1;
}

location [ = | ~ | ~* | ^~] uri {
................
................
}

1. =，用于标准 uri 前，要求请求字符串和 uri 严格匹配。如果匹配成功，就停止向下继续搜索并立即使用该 location 块处理请求
2，~，用于表示 uri 包含正则表达式，并区分大小写
3，~*，用于表示 uri 包含正则表达式，并且不区分大小写
4，^~，用于标准 uri 前，要求 nginx 服务器找到和请求字符串匹配度最高的标准 uri 后，立即使用该 location 快处理请求，不再使用 location 块的正则 uri 和请求字符串做匹配

我们知道浏览器传送 uri 时，会对一部分 uri 进行编码，比如，空格会被编码成 "%20"，问号会被编码成 '%3f"等，"^"有一个特点，它会对 uri 中的这些符号做编码处理，如，如果 location 块接收到的 uri 是 /html/%20/data，则当 nginx 服务器搜索到配置为 /html//data 的 location 块时就可以匹配成功

upstream bakend {
server 192.168.0.14 weight=10;
server 192.168.0.15 weight=10;
}

upstream bakend {
ip_hash;
server 192.168.0.14:88;
server 192.168.0.15:80;
}

upstream backend {
server server1;
server server2;
fair;
}

例：在upstream中加入hash语句，server语句中不能写入weight等其他的参数，hash_method是使用的hash算法
upstream backend {
server squid1:3128;
server squid2:3128;
hash $request_uri;
hash_method crc32;
}

1，down，表示当前机器暂时不参与负载均衡
2，backup，预留的备份机器。当其他所有的非 backup 机器出现故障或忙的时候，才会请求 backup 机器，因为此台机器的访问压力最小
3，max_fails，允许请求的失败次数，默认为 1，当超过最大次数时，返回 proxy_next_upstream 模块定义的错误
4，fail_timeout，请求失败超时时间，在经历了 max_fails 次失败后，暂停服务的时间。max_fails 和 fail_timeout 可以一起使用

upstream linuxidc {
server 10.0.6.108:7080;
server 10.0.0.85:8980;
}

location / {
root hml;
index index.html index.htm;
proxy_pass http://linuxidc;
}