大网数据广告活动
服务器运维问答

How can I set up an nginx reverse proxy combined with try_files?

· 52CE 我爱测

I'd like to call a named location which handles a reverse proxy directive. So I've tried the following lines in my virtual host section: upstream node_upstream { server 127.0.0.1:8000; keepalive 64; } server { server_name my.host…

问题原文

原帖链接 · LongHike · CC BY-SA 4.0

I'd like to call a named location which handles a reverse proxy directive. So I've tried the following lines in my virtual host section:

upstream node_upstream {
    server 127.0.0.1:8000;
    keepalive 64;
}

server {
  server_name my.host-name.com;
  listen 80;  
  access_log  /home/webhost/logs/my-host-name.access.log;
  error_log  /home/webhost/logs/my-host-name.error.log;

  root /home/webhost/www/my.host-name.com/node-canary/public;
  
  location / {
    index index.html; 
    try_files $uri $uri.html $uri/index.html $uri/ @node;
  }

  location @node {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $http_host;
       
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
        
    proxy_pass http://node_upstream/;
    proxy_redirect off;
    proxy_read_timeout 240s;
  }
}

This is pretty straight forward, but on running it, I get

nginx: [emerg] "proxy_pass" cannot have URI part in location
given by regular expression, or inside named location, or inside
"if" statement, or inside "limit_except" block in 
/home/webhost/sites-enabled/my.host-name.com:29
nginx: configuration file /usr/local/etc/nginx/nginx.conf test failed

For me this means I can't use proxy pass in the @node named location.

So, I tought I could outsmart nginx by simply moving the directives located in the @node location into the root (i.e. /) location. Anything outside remains the same. Like this:

server {
  server_name my.host-name.com;
  listen 80;  
  access_log  /home/webhost/logs/my-host-name.access.log;
  error_log  /home/webhost/logs/my-host-name.error.log;

  root /home/webhost/www/my.host-name.com/node-canary/public;
  
  location / {
    index index.html; 
    try_files $uri $uri.html $uri/index.html $uri/ $uri;

    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $http_host;
       
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
        
    proxy_pass http://node_upstream/;
    proxy_redirect off;
    proxy_read_timeout 240s;
  }
}

But with this setup, something weird happens. When an existing static file is being hit, the request is being answered by the proxy connection (a node app) – not by responding with the static file itself.

That's the only case a request returns a valid response. Any route not matching a static file returns a an nginx 500 server error.

This sort of baffles me up to the point of being flabbergasted.

已采纳解答

原帖链接 · Richard Smith · CC BY-SA 4.0

The error message "proxy_pass" cannot have URI part in ... is simply referring to the trailing / in your proxy_pass statement.

Use:

proxy_pass http://node_upstream;

instead of:

proxy_pass http://node_upstream/;

See this document for details.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2022-07-30)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。