为什么我推荐Nginx作为后端服务器代理(原因解析)

 server {
  listen  80;
  server_name felord.cn;
 # ^~ 表示uri以某个常规字符串开头，如果匹配到，则不继续往下匹配。不是正则匹配
  location ^~ /api/v1 {
   proxy_set_header Host $host;
   proxy_pass http://192.168.1.9:8080/;
  }
 }

location ^~ /api/v1 {
 proxy_set_header Host $host;
 if ($request_method = POST){
  return 405;
 }
 proxy_pass http://192.168.1.9:8080/;
}

http{
 #http节点中可以添加多个server节点
 server{
  #ssl 需要监听443端口
  listen 443;
  # CA证书对应的域名
  server_name felord.cn;
  # 开启ssl
  ssl on;
  # 服务器证书绝对路径
  ssl_certificate /etc/ssl/cert_felord.cn.crt;
  # 服务器端证书key绝对路径 
  ssl_certificate_key /etc/ssl/cert_felord.cn.key;
  ssl_session_timeout 5m;
  # 协议类型
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  # ssl算法列表 
  ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:HIGH:!aNULL:!MD5:!RC4:!DHE;
  # 是否 服务器决定使用哪种算法 on/off TLSv1.1 的话需要开启
  ssl_prefer_server_ciphers on;
  
  location ^~ /api/v1 {
   proxy_set_header Host $host;
   proxy_pass http://192.168.1.9:8080/;
  }
 }
 # 如果用户通过 http 访问 直接重写 跳转到 https 这个是一个很有必要的操作
 server{
  listen 80;
  server_name felord.cn;
  rewrite ^/(.*)$ https://felord.cn:443/$1 permanent;
 }

}

http {
 
 upstream app {
   # 节点1
   server 192.168.1.9:8080;
   # 节点2
   server 192.168.1.10:8081;
   # 节点3
   server 192.168.1.11:8082;
 }
 
 server {
  listen  80;
  server_name felord.cn;
 # ^~ 表示uri以某个常规字符串开头，如果匹配到，则不继续往下匹配。不是正则匹配
  location ^~ /api/v1 {
   proxy_set_header Host $host;
   # 负载均衡
   proxy_pass http://app/;
  }
 }
}

upstream app {
  # 节点1
  server 192.168.1.9:8080 weight = 6;
  # 节点2
  server 192.168.1.10:8081 weight = 3;
  # 节点3
  server 192.168.1.11:8082 weight = 1;
}

upstream app {
  ip_hash;
  # 节点1
  server 192.168.1.9:8080 weight = 6;
  # 节点2
  server 192.168.1.10:8081 weight = 3;
  # 节点3
  server 192.168.1.11:8082 weight = 1;
}

upstream app {
  least_conn;
  # 节点1
  server 192.168.1.9:8080 weight = 6;
  # 节点2
  server 192.168.1.10:8081 weight = 3;
  # 节点3
  server 192.168.1.11:8082 weight = 1;
}