nginx經過https方式反向代理多實例tomcat

時間  2019-12-20
標籤 nginx 經過 https 方式 反向 代理 實例 tomcat 欄目 Nginx 简体版
原文   原文鏈接

案例說明：
前面一層nginx+Keepalived部署的LB,後端兩臺web服務器部署了多實例的tomcat，經過https方式部署nginx反向代理tomcat請求。配置一以下：html

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
1）LB層的nginx配置
 
訪問http強制轉到https
[root@external-lb01 ~] # cat /data/nginx/conf/vhosts/80-www.kevin.com.conf
server {
         listen       80;
         server_name  kevin.com www.kevin.com;
 
         access_log   /data/nginx/logs/www .kevin.com-access.log main;
         error_log   /data/nginx/logs/www .kevin.com-error.log;
 
         error_page   500 502 503 504   /50x .html;
         location =  /50x .html {
             root   html;
         }
 
         return       301 https: // $server_name$request_uri;
}
 
 
https反向代理的配置
[root@external-lb01 ~] # cat /data/nginx/conf/vhosts/443-www.kevin.com.conf
upstream scf_cluster {
     ip_hash;
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
upstream portal_cluster {
     ip_hash;
     server 192.168.10.20:9040;
     server 192.168.10.21:9040;
     }
upstream file_cluster{
     ip_hash;
     server 192.168.10.20:9020;
     }
upstream workflow_cluster{
     ip_hash;
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
upstream batch_cluster{
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
 
server {
         listen       443;
         server_name  www.kevin.com;
 
         ssl on;
         ssl_certificate  /data/nginx/conf/ssl/kevin .cer;
         ssl_certificate_key  /data/nginx/conf/ssl/kevin .key;
         ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
         ssl_session_cache    shared:SSL:1m;
         ssl_session_timeout  5m;
         ssl_ciphers  ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4:!DH:!DHE;
         ssl_prefer_server_ciphers  on;
 
         access_log   /data/nginx/logs/www .kevin.com-access.log main;
         error_log   /data/nginx/logs/www .kevin.com-error.log;
 
         error_page   500 502 503 504   /50x .html;
         location =  /50x .html {
             root   html;
         }
 
        rewrite  /portal-pc  https: //www .kevin.com  break ;
 
        location / {
             proxy_pass http: //portal_cluster/portal-pc/ ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
 
             location  /scf  {
             proxy_pass http: //scf_cluster/scf ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
 
         location  /msdp-file  {
             proxy_pass http: //file_cluster/msdp-file ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
         
     location  /upload  {
             proxy_pass http: //file_cluster/upload ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
         
         location  /activiti-workflow-console  {
             proxy_pass http: //workflow_cluster/activiti-workflow-console ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
 
     location  /batch-framework-web  {
             proxy_pass http: //batch_cluster/batch-framework-web ;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             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 X-Forwarded-Proto http;
             proxy_redirect off;
         } 
}
 
 
以上配置中，須要注意：
訪問https: //www .kevin.com 要求和訪問http: //192 .168.10.20:9040 /portal-pc/  結果一致
訪問https: //www .kevin.com /portal-pc  要求和訪問https: //www .kevin.com 結果一致
 
 
2）後端兩臺機器192.168.10.20和192.168.10.21的tomcat配置。兩臺配置一致，這裏以192.168.10.20配置爲例：
[root@bl2-app01 ~] # cat /data/release/projects/tomcat_app_9020/conf/server.xml
......
     <Connector port= "9020"  protocol= "HTTP/1.1"
                connectionTimeout= "20000"
                redirectPort= "8443"  URIEncoding= "UTF-8" />
......
     <Connector port= "9029"  protocol= "AJP/1.3"  redirectPort= "8443"  />
 
 
[root@bl2-app01 ~] # cat /data/release/projects/tomcat_portal_9040/conf/server.xml
......
<Connector port= "9040"  protocol= "HTTP/1.1"
                connectionTimeout= "20000"
                redirectPort= "4443"  URIEncoding= "UTF-8" />
......
     <Connector port= "9049"  protocol= "AJP/1.3"  redirectPort= "4443"  />
.....

===============================================================================
配置二：也能夠採用以下proxy_redirect配置（指定修改被代理服務器返回的響應頭中的location頭域跟refresh頭域數值）（注意下面proxy_redirect裏由http -> https的代理返回設置）前端

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
[root@external-lb01 ~] # cat /data/nginx/conf/vhosts/443-www.kevin.com.conf
upstream scf_cluster {
     ip_hash;
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
upstream portal_cluster {
     ip_hash;
     server 192.168.10.20:9040;
     server 192.168.10.21:9040;
     }
upstream file_cluster{
     ip_hash;
     server 192.168.10.20:9020;
     }
upstream workflow_cluster{
     ip_hash;
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
upstream batch_cluster{
     server 192.168.10.20:9020;
     server 192.168.10.21:9020;
     }
   
server {
         listen       443;
         server_name  www.kevin.com;
   
         ssl on;
         ssl_certificate  /data/nginx/conf/ssl/bigtree .cer;
         ssl_certificate_key  /data/nginx/conf/ssl/bigtree .key;
         ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
         ssl_session_cache    shared:SSL:1m;
         ssl_session_timeout  5m;
         ssl_ciphers  ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4:!DH:!DHE;
         ssl_prefer_server_ciphers  on;
   
         access_log   /data/nginx/logs/www .kevin.com-access.log main;
         error_log   /data/nginx/logs/www .kevin.com-error.log;
   
         error_page   500 502 503 504   /50x .html;
         location =  /50x .html {
             root   html;
         }
   
         location  /scf  {
             proxy_pass http: //scf_cluster/scf ;
             proxy_redirect  http: //scf_cluster/scf  https: //www .kevin.com /scf ;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
   
         location / {
             proxy_pass http: //portal_cluster/portal-pc/ ;
             proxy_redirect  http: //portal_cluster/portal-pc/  https: //www .kevin.com/;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
   
         location  /msdp-file  {
             proxy_pass http: //file_cluster/msdp-file ;
             proxy_redirect  http: //file_cluster/msdp-file  https: //www .kevin.com /msdp-file ;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
           
         location  /upload  {
             proxy_pass http: //file_cluster/upload ;
             proxy_redirect  http: //file_cluster/upload  https: //www .kevin.com /upload ;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
           
         location  /activiti-workflow-console  {
             proxy_pass http: //workflow_cluster/activiti-workflow-console ;
             proxy_redirect  http: //workflow_cluster/activiti-workflow-console  https: //www .kevin.com /activiti-workflow-console ;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
   
         location  /batch-framework-web  {
             proxy_pass http: //batch_cluster/batch-framework-web ;
             proxy_redirect  http: //batch_cluster/batch-framework-web  https: //www .kevin.com /batch-framework-web ;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_connect_timeout 300;
             proxy_send_timeout 300;
             proxy_read_timeout 600;
             proxy_buffer_size 256k;
             proxy_buffers 4 256k;
             proxy_busy_buffers_size 256k;
             proxy_temp_file_write_size 256k;
             proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
             proxy_max_temp_file_size 128m;
         }
}
 
======================舒適提示========================
上面啓用了proxy_redirect配置（http->https），配置中就不須要 "proxy_set_header Host $host;" ，即不須要 "添加發日後端服務器的請求頭" 的配置了

================================================================================
如上，配置了80端口的http訪問強制跳轉爲443端口的https訪問方式：
1）若是域名配置爲https的訪問方式，則上面配置一和配置二均可以。
2）若是域名配置爲http的訪問方式，則如上配置一後，訪問的結果都只會跳轉到https的首頁，故這種狀況下需如上配置二。nginx

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
以下，訪問http: //bpm .kevin.com的結果只會在強制跳轉爲https: //www .kevin.com
[root@external-lb01 ~] # cat /data/nginx/conf/vhosts/bpm.kevin.com.conf
upstream os-8080 {
       #ip_hash;
       server 192.168.10.20:8080 max_fails=3 fail_timeout=15s;
       server 192.168.10.21:8080 max_fails=3 fail_timeout=15s;
}
             
server {
       listen      80;
       server_name bpm.kevin.com;
       
       access_log   /data/nginx/logs/bpm .kevin.com-access.log main;
       error_log   /data/nginx/logs/bpm .kevin.com-error.log;
       
location / {
       proxy_pass http: //os-8080 ;
       proxy_redirect off ;
       proxy_set_header Host $host;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header REMOTE-HOST $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_connect_timeout 300;
       proxy_send_timeout 300;
       proxy_read_timeout 600;
       proxy_buffer_size 256k;
       proxy_buffers 4 256k;
       proxy_busy_buffers_size 256k;
       proxy_temp_file_write_size 256k;
       proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
       proxy_max_temp_file_size 128m;
       #proxy_cache mycache;                             
       #proxy_cache_valid 200 302 1h;
       #proxy_cache_valid 301 1d;
       #proxy_cache_valid any 1m;
     }
       
     error_page   500 502 503 504   /50x .html;
     location =  /50x .html {
         root   html;
     }
}
   
   
若是想要訪問http: //bpm .kevin.com的結果不強制跳轉爲https: //www .kevin.com，則須要啓用proxy_redirect的配置：
[root@external-lb01 ~] # cat /data/nginx/conf/vhosts/bpm.kevin.com.conf
upstream os-8080 {
       #ip_hash;
       server 192.168.10.20:8080 max_fails=3 fail_timeout=15s;
       server 192.168.10.21:8080 max_fails=3 fail_timeout=15s;
}
             
   server {
       listen      80;
       server_name bpm.kevin.com;
       
       access_log   /data/nginx/logs/bpm .kevin.com-access.log main;
       error_log   /data/nginx/logs/bpm .kevin.com-error.log;
       
  location / {
       proxy_pass http: //os-8080 ;
       proxy_set_header Host $host;     // 注意這個是http請求，沒有http->https轉發需求，必需要加上這個proxy_set_header設置，不然代理轉發返回的頭信息會有誤！
       proxy_redirect  http: //os-8080/  http: //bpm .kevin.com/;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504 http_404;
     }
   
     error_page   500 502 503 504   /50x .html;
     location =  /50x .html {
     root   html;
     }
}

===============================================================================
nginx作前端代理分發，tomcat處理請求。nginx反代tomcat實現https有二個方法web

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
1、nginx配置https，tomcat也配置https
1）nginx配置https
upstream https_tomcat_web { 
         server 127.0.0.1:8443; 
} 
   
server { 
         listen       443; 
         server_name  www. test .com; 
         index index.html; 
         root    /var/www/html/test ; 
   
         ssl on; 
         ssl_certificate  /etc/nginx/go .pem; 
         ssl_certificate_key  /etc/nginx/go .key; 
         ssl_session_timeout 5m; 
         ssl_protocols SSLv2 SSLv3 TLSv1.2; 
#        ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; 
         ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4; 
         ssl_prefer_server_ciphers on; 
   
         location ~ ^ /admin  { 
             proxy_pass https: //https_tomcat_web ;   // 是https的 
             proxy_redirect                      off; 
             proxy_set_header   Host             $host; 
             proxy_set_header   X-Real-IP        $remote_addr; 
             proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for; 
             client_max_body_size       100m; 
             client_body_buffer_size    256k; 
             proxy_connect_timeout      60; 
             proxy_send_timeout         30; 
             proxy_read_timeout         30; 
             proxy_buffer_size          8k; 
             proxy_buffers              8 64k; 
             proxy_busy_buffers_size    64k; 
             proxy_temp_file_write_size 64k; 
         } 
   
         error_page 404  /404 .html; 
         location =  /40x .html { 
         } 
   
         error_page 500 502 503 504  /50x .html; 
   
         location =  /50x .html { 
         } 
   
} 
 
 
2）tomcat的https配置,配置文件server.xml
<Service name= "Catalina" > 
  <Connector port= "8001"  protocol= "HTTP/1.1" 
  connectionTimeout= "20000" 
  redirectPort= "8443"  /> 
   
  <Connector port= "8091" 
  protocol= "AJP/1.3" 
  redirectPort= "8443"  /> 
   
// 添加如下內容 
  <Connector port= "8443" 
  protocol= "HTTP/1.1" 
  SSLEnabled= "true" 
  scheme= "https" 
  secure= "false" 
  keystoreFile= "cert/gotom.pfx" 
  keystoreType= "PKCS12" 
  keystorePass= "214261272770418" 
  clientAuth= "false" 
  SSLProtocol= "TLSv1+TLSv1.1+TLSv1.2" 
  ciphers= "TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256"  /> 
   
  ..................省略.................... 
  < /Service > 
 
 
  配置好後從新啓動nginx，tomcat，就能夠https訪問了，這也是如今比較常見採用的配置方式 。
 
 
 
2、nginx採用https，tomcat採用http
1）nginx配置https
upstream https_tomcat_web { 
         server 127.0.0.1:8001; 
} 
   
server { 
         listen       443; 
         server_name  www. test .com; 
         index index.html; 
         root    /var/www/html/test ; 
   
         ssl on; 
         ssl_certificate  /etc/nginx/go .pem; 
         ssl_certificate_key  /etc/nginx/go .key; 
         ssl_session_timeout 5m; 
         ssl_protocols SSLv2 SSLv3 TLSv1.2; 
#        ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; 
         ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4; 
         ssl_prefer_server_ciphers on; 
   
         location ~ ^ /admin  { 
             proxy_pass http: //https_tomcat_web ;   // 是http的 
             proxy_redirect                      off; 
             proxy_set_header   Host             $host; 
             proxy_set_header   X-Real-IP        $remote_addr; 
             proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for; 
             client_max_body_size       100m; 
             client_body_buffer_size    256k; 
             proxy_connect_timeout      60; 
             proxy_send_timeout         30; 
             proxy_read_timeout         30; 
             proxy_buffer_size          8k; 
             proxy_buffers              8 64k; 
             proxy_busy_buffers_size    64k; 
             proxy_temp_file_write_size 64k; 
         } 
   
         error_page 404  /404 .html; 
         location =  /40x .html { 
         } 
   
         error_page 500 502 503 504  /50x .html; 
   
         location =  /50x .html { 
         } 
   
} 
 
2）tomcat的http配置,配置文件server.xml
<Service name= "Catalina" > 
  <Connector port= "8001"  protocol= "HTTP/1.1" 
  connectionTimeout= "20000" 
  redirectPort= "443"  />     // 在這裏從新定向到了443端口 
   
  <Connector port= "8091" 
  protocol= "AJP/1.3" 
  redirectPort= "443"  /> 
   
  ..................省略.................... 
  < /Service > 
重啓nginx，tomcat，https就配置好了。

=====================Nginx非80端口代理轉發配置=======================
注意：nginx使用非80端口轉發時，proxy_set_header配置中的$host後面必定要跟端口！以下篇配置（proxy_set_header Host $host:8080; ）。不然訪問會有問題！（當https訪問時，已配置了http強轉https，則$host後面不需加443端口）。後端

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
[root@ng-lb01 vhosts] # cat fax.kevin.com.conf
upstream fax {
       server 192.168.10.34:8080;
}
           
   server {
       listen      8080;
       server_name fax.kevin.com;
     
       access_log   /data/nginx/logs/fax .kevin.com-access.log main;
       error_log   /data/nginx/logs/fax .kevin.com-error.log;
 
     location / {
             proxy_pass http: //fax ;
             proxy_set_header Host $host:8080;
             proxy_set_header X-Real-IP $remote_addr;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_set_header X-Forwarded-Proto http;
             proxy_redirect off;
 
         }
 
         error_page   500 502 503 504   /50x .html;
         location =  /50x .html {
             root   html;
         }
}
相關文章
相關標籤/搜索
每日一句
    每一个你不满意的现在，都有一个你没有努力的曾经。
本站公眾號
   歡迎關注本站公眾號,獲取更多信息
聯繫我們 最近搜索 最新文章 沪ICP备13005482号-10 MyBatis教程 SQL 教程 MySQL教程 Java 教程 Thymeleaf 教程 Hibernate教程 Spring教程 Redis教程