nginx使用proxy_pass反向代理，cookie丢失的问题

太过爱你忘了你带给我的痛 2021-09-27 22:56 1047阅读 0赞

1. 如果只是host、端口转换，则cookie不会丢失。例如：  
    location /project \{  
        proxy\_pass   http://127.0.0.1:8080/project;  
    \}

通过浏览器访问http://127.0.0.1/project时，浏览器的cookie内有jsessionid。再次访问时，浏览器会发送当前的cookie。

2. 如果路径也变化了，则需要设置cookie的路径转换，nginx.conf的配置如下  
    location /proxy\_path \{  
        proxy\_pass   http://127.0.0.1:8080/project;  
    \}

通过浏览器访问http://127.0.0.1/proxy\_path时，浏览器的cookie内没有jsessionid。再次访问时，后台当然无法获取到cookie了。  
详细看了文档：http://nginx.org/en/docs/http/ngx\_http\_proxy\_module.html?&\_ga=1.161910972.1696054694.1422417685\#proxy\_cookie\_path

加上路径转换：proxy\_cookie\_path  /project /proxy\_path;  
则可以将project的cookie输出到proxy\_path上。正确的配置是：

location /proxy\_path \{  
        proxy\_pass   http://127.0.0.1:8080/project;  
        proxy\_cookie\_path  /project /proxy\_path;  
    \}

nignx配置文件从上往下匹配，匹配到就不在匹配，配置文件如果带项目名则需要注意proxy\_cookie\_path参数

例如

location / {
                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_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
                proxy_max_temp_file_size 0;
                proxy_connect_timeout      30;
                proxy_send_timeout         30;
                proxy_read_timeout         30;
                proxy_buffer_size          4k;
                proxy_buffers              4 32k;
                proxy_busy_buffers_size    64k;
                proxy_temp_file_write_size 64k;
                proxy_pass http://47.104.107.100:8080/article-web/;
    	    	#proxy_cookie_path /article-web /;
            }
    
        
         
     
            # 所有动态请求都转发给tomcat处理  
            location /article-web {  
                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_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
               # proxy_max_temp_file_size 0;
                proxy_connect_timeout      30;
                proxy_send_timeout         30;
                proxy_read_timeout         30;
                proxy_buffer_size          4k;
                proxy_buffers              4 32k;
                proxy_busy_buffers_size    64k;
                proxy_temp_file_write_size 64k;
                proxy_pass http://47.104.107.100:8080/article-web/;         
               	proxy_cookie_path /article-web /;
            }