Linux 下 nginx反向代理與負載均衡
阿新 • • 發佈:2018-11-15
前面幾篇記錄下nginx的基本運功,代理伺服器的訪問,這裡來試驗下nginx的反向代理。
反向代理(Reverse Proxy)方式是指以 代理伺服器來接受internet上的連線請求,然後將請求轉發給內部網路上的伺服器,並將從伺服器上得到的結果返回給internet上請求連線的客戶端,此時代理伺服器對外就表現為一個反向代理伺服器。在我們的java專案中的體現就是,通過80埠訪問,Nginx接收到,然後進行轉發給tomcat伺服器,再將伺服器的結果給返回。
這裡需要修改nginx.conf檔案。
upstream backend { #代理的IP weight權重大的,接收的訪問量就大,反之 server localhost:8084 weight=50; server localhost:8088 weight=50; }
將接收的請求進行轉發:
# / 所有做負載均衡 + 反向代理 location / { root /data/wwwroot1; index index.html index.htm;#索引檔案 proxy_pass http://backend; }
這樣,通過請求nginx的請求,就可以被分配轉發到tomcat上去。這裡我是定義了兩臺tomcat伺服器,同時用來做負載均衡的處理。通過設定weight,可以控制訪問量。
具體配置程式碼如下;
#user nobody; # worker 工作程序 一般設定 CPU數 * 核數 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;#1個worker產生多少個連線數 } # 配置HTTP伺服器的主要段 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壓縮功能設定 gzip on; gzip_min_length 1k; gzip_buffers 4 16k; gzip_http_version 1.0; gzip_comp_level 6; gzip_types text/plain text/css text/javascript application/json application/javascript application/x-javascript application/xml; gzip_vary on; #設定負載均衡後臺伺服器列表 upstream backend { #代理的IP weight權重大的,接收的訪問量就大,反之 server localhost:8084 weight=50; server localhost:8088 weight=50; } server { listen 2022; server_name localhost; charset utf-8; access_log logs/wwwroot2.access.log main; location / { root /data/wwwroot2; index index.html index.htm;#索引檔案 } } # 虛擬主機段 server { listen 80; server_name localhost; root /data/wwwroot1; charset utf-8; #訪問日誌 access_log logs/wwwroot1.access.log main; # / 所有做負載均衡 + 反向代理 location / { root /data/wwwroot1; index index.html index.htm;#索引檔案 proxy_pass http://backend; } 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; # } #} }
測試結果發現,通過訪問80埠的地址,展現的結果是基本五五開的。
還會隨機訪問到
以上兩個截圖,分別對應了我的兩個tomcat伺服器下的測試檔案。