linux下nginx【反向代理】配置【负载均衡】配置

nginx 安装过程略过,新手可参考nginx安装教程 本次主要记录下nginx配置文件的设置过程

nginx 的 配置文件nginx.conf 可以配置多个端口

复制一个  server{   //code }  代码块  修改端口即可

如下配置文件中 nginx 启动后,可访问以下两个端口。

修改后配置文件后 ,访问  http://ip:10088  和 http://ip:10087 均可请求到nginx服务。

1、10088端口 配置反向代理,消除跨域问题。

在 server { //code} 中添加如下代码 则可以添加一个Tomcat 服务的反向代理。

原始访问tomcat 的路径 为 http://ip:8582/ncms  在 nginx 配置文件中加入以下代码 后,则可以通过 http://ip:10088/ncms  访问到 tomcat的服务。

这对于在一台服务器上发布多个tomcat时 统一的地址端口+不同项目,可以完美绕开跨域问题。

 location /ncms {
proxy_pass http://127.0.0.1:8582;
proxy_set_header Host $host:10088;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
}

  

2、10087端口 配置ip_hash模式的负载均衡,ip_hash可以绕开解决session共享的问题。

目前许多应用均为多节点部署。

例如:同一个java Web应用 部署了4个 Tomcat 服务,把tomcat原始访问地址+端口配置成如下模式, weight为权重。

以下配置模式表示  server 10.174.25.213:8582 weight=6 有60%的概率处理客户端请求。

用ip_hash表示 客户端的请求被分配到某一服务器上, 直到会话退出始终会请求该服务器,这样用户请求就不会再被分配到其他服务器导致 session 失效的问题。
    upstream tomcatsncms {
server 10.174.25.213: weight=;
server 10.174.25.45: weight=;
server 10.174.25.48: weight=;
server 10.174.25.49: weight=;
ip_hash; }

在 server{ //code }中添加如下代码 配置外网访问的端口, 这样 用户再次请求  http://ip+10087/ncms 时 实际会去被分配到后台部署的4台server中去 ,

值得一提的是如果某一台tomcat服务器宕机或者停机维护,都不会影响正常服务。

负载均衡不仅分流的前台用户的请求到不同的机器,而且如果某一个节点坏死会自动判断把请求分流到正常的tomcat服务器上。

        location /ncms {
proxy_pass http://tomcatsncms;
proxy_set_header Host $host:;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
}

附一份修改配置后完整的nginx.conf具体配置文件如下:

#user  nobody;
worker_processes 1; #error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info; #pid logs/nginx.pid; events {
worker_connections 1024;
} 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 logs/access.log main; sendfile on;
#tcp_nopush on; #keepalive_timeout 0;
keepalive_timeout 65; #gzip on; upstream tomcatsncms {
server 10.174.25.213:8582 weight=6;
server 10.174.25.45:8582 weight=1;
server 10.174.25.48:8582 weight=1;
server 10.174.25.49:8582 weight=1;
ip_hash; }
upstream tomcatsfir {
server 10.174.25.213:8583 weight=6;
server 10.174.25.45:8583 weight=1;
server 10.174.25.48:8583 weight=1;
server 10.174.25.49:8583 weight=1;
ip_hash;
} server {
listen 10087;
server_name localhost; #charset koi8-r; #access_log logs/host.access.log main; location / {
root html;
index index.html index.htm;
}
location /ncms {
proxy_pass http://tomcatsncms;
proxy_set_header Host $host:10087;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
}
location /fir {
proxy_pass http://tomcatsfir;
proxy_set_header Host $host:10087;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
} #error_page 404 /404.html; # redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
} # proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#} # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#} # deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
} server {
listen 10088;
server_name localhost; #charset koi8-r; #access_log logs/host.access.log main; location / {
root html;
index index.html index.htm;
}
location /ncms {
proxy_pass http://127.0.0.1:8582;
proxy_set_header Host $host:10088;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
}
location /fir {
proxy_pass http://127.0.0.1:8582;
proxy_set_header Host $host:10088;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
}
location /docs {
proxy_pass http://127.0.0.1:8582;
proxy_set_header Host $host:10088;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Via "nginx";
client_max_body_size 50m;
} #error_page 404 /404.html; # redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
} # proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#} # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#} # deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
} # another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
# listen 8000;
# listen somename:8080;
# server_name somename alias another.alias; # location / {
# root html;
# index index.html index.htm;
# }
#} # HTTPS server
#
#server {
# listen 443 ssl;
# server_name localhost; # ssl_certificate cert.pem;
# ssl_certificate_key cert.key; # ssl_session_cache shared:SSL:1m;
# ssl_session_timeout 5m; # ssl_ciphers HIGH:!aNULL:!MD5;
# ssl_prefer_server_ciphers on; # location / {
# root html;
# index index.html index.htm;
# }
#} }

  

上一篇:点击按钮,回到页面顶部的5种写法


下一篇:[深入浅出Cocoa]iOS网络编程之Socket