需求如下：研发代码里写死了地址 https://b.com 现在在不想发布新代码的情况下修改地址为 https://a.com

手动增加反向代理的 header

先 ping a.com 获取到服务器的 ip

所以临时在 pod 里面新增了 nginx 服务，配置如下，由于是代理 https 服务，还需要配置 ssl 证书，刚好有证书。。。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
server {
  listen 80;
  listen [::]:80;
  listen 443 ssl;
  listen [::]:443 ssl;
  ssl_certificate   /etc/nginx/ssl.crt;
  ssl_certificate_key /etc/nginx/ssl.key;
  ssl_session_timeout 5m;
  ssl_ciphers HIGH:!aNULL:!MD5;
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  ssl_prefer_server_ciphers on;
  server_name b.com;
  client_max_body_size 1024m;


  location / {
    proxy_pass https://139.224.186.170;                        # ping 出来的域名IP
    proxy_set_header HOST a.com;                  # 增加header HOST: a.com
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
}

优化写法

nginx 提供了内置变量 $proxy_host，优化写法为：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
server {
  listen 80;
  listen [::]:80;
  listen 443 ssl;
  listen [::]:443 ssl;
  ssl_certificate   /etc/nginx/ssl.crt;
  ssl_certificate_key /etc/nginx/ssl.key;
  ssl_session_timeout 5m;
  ssl_ciphers HIGH:!aNULL:!MD5;
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  ssl_prefer_server_ciphers on;
  server_name b.com;
  client_max_body_size 1024m;

  location / {
    proxy_pass https://a.com;
    proxy_set_header HOST $proxy_host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
}

本地绑定 hosts

1
127.0.0.1   b.com

测试效果

这个时候两个域名访问效果一模一样了.

访问效果