企业官网建设流程全解析

做淘客网站要什么样服务器,万网域名信息,网页怎么做网站地图,杭州网站推广概述 Nginx 配置中 location 和 proxy_pass 指令的不同组合方式及其对请求转发路径的影响。 配置效果 1. location 和 proxy_pass 都带斜杠 / location /api/ {proxy_pass http://127.0.0.1:8080/; }访问地址#xff1a;www.hw.com/api/upload转发地址#xff1a;http://127.…概述Nginx 配置中location和proxy_pass指令的不同组合方式及其对请求转发路径的影响。配置效果1.location和proxy_pass都带斜杠/location /api/ { proxy_pass http://127.0.0.1:8080/; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/upload转发地址不带 location 匹配目录 /api/2.location不带斜杠proxy_pass带斜杠/location /api { proxy_pass http://127.0.0.1:8080/; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080//upload转发地址会多带 /3.location带斜杠proxy_pass不带斜杠location /api/ { proxy_pass http://127.0.0.1:8080; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/api/upload转发地址会带 location 匹配目录 /api/4.location和proxy_pass都不带斜杠location /api { proxy_pass http://127.0.0.1:8080; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/api/upload转发地址会带 location 匹配目录 /api/5.location和proxy_pass都带斜杠/但proxy_pass带地址location /api/ { proxy_pass http://127.0.0.1:8080/server/; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/server/upload转发地址不带 location 匹配目录 /api/6.location不带斜杠proxy_pass带斜杠/但proxy_pass带地址location /api { proxy_pass http://127.0.0.1:8080/server/; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/server//upload转发地址不带 location 匹配目录 /api/ 会多带 /7.location带斜杠proxy_pass不带斜杠但proxy_pass带地址location /api/ { proxy_pass http://127.0.0.1:8080/server; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/serverupload转发地址不带 location 匹配目录 /api/ 直接进行了替换8.location和proxy_pass都不带斜杠但proxy_pass带地址location /api { proxy_pass http://127.0.0.1:8080/server; }访问地址www.hw.com/api/upload转发地址http://127.0.0.1:8080/server/upload转发地址不带 location 匹配目录 /api总结当proxy_pass代理地址端口后有目录包括/转发后地址为代理地址 访问 URL 目录部分去除location匹配目录。当proxy_pass代理地址端口后无任何内容转发后地址为代理地址 访问 URL 目录部分包括location地址。场景示例upstream backend_name_hw { server 10.10.10.10:32323 max_fails2 fail_timeout2; } server { listen 80; server_name hw.test.com; client_max_body_size 1024m; client_body_timeout 12; client_header_timeout 12; keepalive_timeout 15; send_timeout 10; location / { proxy_pass http://backend_name_hw; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location /hello { proxy_pass http://backend_name_hw/hello; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }location /hw/ { proxy_pass http://hw-nginx/index.html; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }location /hwhw/ { proxy_pass http://hw-nginx/; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }location /hw/hi/ { proxy_pass http://hw-nginx/hello/index.html; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }location /hello/index.html { proxy_pass http://hw-nginx; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }